A CertificateRequest is used to request a signed certificate from one of the configured issuers. All fields within the CertificateRequest's `spec` are immutable after creation. A CertificateRequest will either succeed or fail, as denoted by its `status.state` field. A CertificateRequest is a one-shot resource, meaning it represents a single point in time request for a certificate and cannot be re-used.
5 top-level fields, 1 required · last changed in cert-manager v1.3.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Desired state of the CertificateRequest resource.
The requested 'duration' (i.e. lifetime) of the Certificate. This option may be ignored/overridden by some issuer types.
Extra contains extra attributes of the user that created the CertificateRequest. Populated by the cert-manager webhook on creation and immutable.
Groups contains group membership of the user that created the CertificateRequest. Populated by the cert-manager webhook on creation and immutable.
IsCA will request to mark the certificate as valid for certificate signing when submitting to the issuer. This will automatically add the `cert sign` usage to the list of `usages`.
IssuerRef is a reference to the issuer for this CertificateRequest. If the `kind` field is not set, or set to `Issuer`, an Issuer resource with the given name in the same namespace as the CertificateRequest will be used. If the `kind` field is set to `ClusterIssuer`, a ClusterIssuer with the provided name will be used. The `name` field in this stanza is required at all times. The group field refers to the API group of the issuer which defaults to `cert-manager.io` if empty.
Group of the resource being referred to.
Kind of the resource being referred to.
Name of the resource being referred to.
The PEM-encoded x509 certificate signing request to be submitted to the CA for signing.
UID contains the uid of the user that created the CertificateRequest. Populated by the cert-manager webhook on creation and immutable.
Usages is the set of x509 usages that are requested for the certificate. If usages are set they SHOULD be encoded inside the CSR spec Defaults to `digital signature` and `key encipherment` if not specified.
Username contains the name of the user that created the CertificateRequest. Populated by the cert-manager webhook on creation and immutable.
Status of the CertificateRequest. This is set and managed automatically.
The PEM encoded x509 certificate of the signer, also known as the CA (Certificate Authority). This is set on a best-effort basis by different issuers. If not set, the CA is assumed to be unknown/not available.
The PEM encoded x509 certificate resulting from the certificate signing request. If not set, the CertificateRequest has either not been completed or has failed. More information on failure can be found by checking the `conditions` field.
List of status conditions to indicate the status of a CertificateRequest. Known condition types are `Ready` and `InvalidRequest`.
LastTransitionTime is the timestamp corresponding to the last status change of this condition.
Message is a human readable description of the details of the last transition, complementing reason.
Reason is a brief machine readable explanation for the condition's last transition.
Status of the condition, one of (`True`, `False`, `Unknown`).
Type of the condition, known values are (`Ready`, `InvalidRequest`, `Approved`, `Denied`).
FailureTime stores the time that this CertificateRequest failed. This is used to influence garbage collection and back-off.
Source: cert-manager.yaml
Changes to CertificateRequest (cert-manager.io/v1) in each cert-manager version, compared to the version before it.
4 properties have been added
1 property has changed the description
Released · View CertificateRequest in v1.3.0
The description of CertificateRequest has changed
3 properties have changed the description
Released · View CertificateRequest in v1.2.0
CertificateRequest was first seen on this version of cert-manager
Released · View CertificateRequest in v1.0.0
No examples of CertificateRequest yet. Contribute one on GitHub.
kubespec.dev