A ‘CertificateRequest’ is a resource in cert-manager that is used to request x509 certificates from an issuer. The resource contains a base64 encoded string of a PEM encoded certificate request which is sent to the referenced issuer. A successful issuance will return a signed certificate, based on the certificate signing request. ‘CertificateRequets’ are typically consumed and managed by controllers or other systems and should not be used by humans - unless specifically needed.
To enable cert-manager’s internal CertificateRequest controllers, supply the following feature gate: –feature-gates=CertificateRequestControllers=true
A simple CertificateRequest looks like the following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14
This CertificateRequest will make cert-manager attempt to make the Issuer
letsencrypt-prod in the default issuer pool
certmanager.k8s.io, return a
certificate based upon the certificate signing request. Other groups can be
specified inside the
issuerRef which will change the targeted issuers to other
external, third party issuers you may have installed.
The resource also exposes the option for stating the certificate as CA and requested validity duration.
A successful issuance of the certificate signing request will cause an update to the resource, setting the status with the signed certificate, the CA of the certificate (if available), and setting the Ready condition to True.
Whether issuance of the controller was successful or not, a retry of the issuance will _not_ happen. It is the responsibility of some other controller to manage the logic and life cycle of CertificateRequets.
CertificateRequests have a set of strongly defined conditions that should be used and relied upon by controllers or services to make decisions on what actions to take next on the resource. Each condition consists of the pair Ready - a boolean value, and Reason - a string. The set of values and meanings are as follows:
|False||Pending||The CertificateRequest is currently pending, waiting for some other operation to take place. This could be that the Issuer does not exist yet or the Issuer is in the process of issuing a certificate.|
|False||Failed||The certificate has failed to be issued - either the returned certificate failed to be decoded or an instance of the referenced issuer used for signing failed. No further action will be taken on the CertificateRequest by it’s controller.|
|True||Issued||A signed certificate has been successfully issued by the referenced Issuer.|