Konubinix' opinionated web of thoughts

Cert-Manager

fleeting

If the name field is specified, cert-manager will edit the named ingress resource in order to solve HTTP01 challenges

https://cert-manager.io/docs/configuration/acme/— http01/

useful for compatibility with ingress controllers such as ingress-gce, which utilize a unique IP address for each Ingress resource created.

https://cert-manager.io/docs/configuration/acme/— http01/

cert-manager offers two challenge validations - HTTP01 and DNS01 challenges.

https://cert-manager.io/docs/configuration/acme/

When a HTTP01 challenge is created, cert-manager will automatically configure your cluster ingress to route traffic for this URL to a small web server that presents this key

https://cert-manager.io/docs/configuration/acme/

. To successfully request a certificate, cert-manager must solve ACME Challenges

https://cert-manager.io/docs/concepts/acme-orders-challenges/

order represents a single certificate request which will be created automatically once a new CertificateRequest resource referencing an ACME issuer has been created. CertificateRequest resources are created automatically by cert-manager once a Certificate resource is created, has its specification changed, or needs renewal.

https://cert-manager.io/docs/concepts/acme-orders-challenges/

the Certificate resource represents a human readable definition of a certificate request that is to be honored by an issuer which is to be kept up-to-date.

https://cert-manager.io/docs/usage/certificate/

usual way that you will interact with cert-manager to request signed certificates

https://cert-manager.io/docs/usage/certificate/

Secret needs to be manually deleted if it is no longer needed

https://cert-manager.io/docs/usage/certificate/

would prefer the Secret to be deleted automatically when the Certificate is deleted, you need to configure your installation to pass the –enable-certificate-owner-ref flag to the controller.

https://cert-manager.io/docs/usage/certificate/

TLS signed certificates to secure your ingress resources.

https://cert-manager.io/docs/usage/ingress/

ingress-shim watches Ingress resources across your cluster.

https://cert-manager.io/docs/usage/ingress/

ensure a Certificate resource with the name provided in the tls.secretName field and configured as described on the Ingress exists

https://cert-manager.io/docs/usage/ingress/

following annotations on Ingress resources in order to trigger Certificate resources to be automatically created

https://cert-manager.io/docs/usage/ingress/

small sub-component of cert-manager, ingress-shim, is responsible for this

https://cert-manager.io/docs/usage/ingress/

Notes pointant ici