You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _/CustomResourceDefinition/certificaterequests.cert-manager.io.yaml
+31-31Lines changed: 31 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ spec:
57
57
description: >-
58
58
A CertificateRequest is used to request a signed certificate from
59
59
one of the configured issuers.
60
-
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.
60
+
All fields within the CertificateRequest's `spec` are immutable after creation. A CertificateRequest will either succeed or fail, as denoted by its `Ready` status condition and its `status.failureTime` field.
61
61
A CertificateRequest is a one-shot resource, meaning it represents a single point in time request for a certificate and cannot be re-used.
62
62
properties:
63
63
apiVersion:
@@ -79,12 +79,16 @@ spec:
79
79
metadata:
80
80
type: object
81
81
spec:
82
-
description: Desired state of the CertificateRequest resource.
82
+
description: >-
83
+
Specification of the desired state of the CertificateRequest
The requested 'duration' (i.e. lifetime) of the Certificate.
87
-
This option may be ignored/overridden by some issuer types.
89
+
Requested 'duration' (i.e. lifetime) of the Certificate.
90
+
Note that the issuer may choose to ignore the requested
91
+
duration, just like any other requested attribute.
88
92
type: string
89
93
extra:
90
94
additionalProperties:
@@ -107,22 +111,19 @@ spec:
107
111
x-kubernetes-list-type: atomic
108
112
isCA:
109
113
description: >-
110
-
IsCA will request to mark the certificate as valid for
111
-
certificate signing when submitting to the issuer. This will
112
-
automatically add the `cert sign` usage to the list of
113
-
`usages`.
114
+
Requested basic constraints isCA value. Note that the issuer
115
+
may choose to ignore the requested isCA value, just like any
116
+
other requested attribute.
117
+
NOTE: If the CSR in the `Request` field has a BasicConstraints extension, it must have the same isCA value as specified here.
118
+
If true, this will automatically add the `cert sign` usage to the list of requested `usages`.
114
119
type: boolean
115
120
issuerRef:
116
121
description: >-
117
-
IssuerRef is a reference to the issuer for this
118
-
CertificateRequest. If the `kind` field is not set, or set
119
-
to `Issuer`, an Issuer resource with the given name in the
120
-
same namespace as the CertificateRequest will be used. If
121
-
the `kind` field is set to `ClusterIssuer`, a ClusterIssuer
122
-
with the provided name will be used. The `name` field in
123
-
this stanza is required at all times. The group field refers
124
-
to the API group of the issuer which defaults to
125
-
`cert-manager.io` if empty.
122
+
Reference to the issuer responsible for issuing the
123
+
certificate. If the issuer is namespace-scoped, it must be
124
+
in the same namespace as the Certificate. If the issuer is
125
+
cluster-scoped, it can be used from any namespace.
126
+
The `name` field of the reference must always be specified.
126
127
properties:
127
128
group:
128
129
description: Group of the resource being referred to.
@@ -138,8 +139,9 @@ spec:
138
139
type: object
139
140
request:
140
141
description: >-
141
-
The PEM-encoded x509 certificate signing request to be
142
-
submitted to the CA for signing.
142
+
The PEM-encoded X.509 certificate signing request to be
143
+
submitted to the issuer for signing.
144
+
If the CSR has a BasicConstraints extension, its isCA attribute must match the `isCA` value of this CertificateRequest. If the CSR has a KeyUsage extension, its key usages must match the key usages in the `usages` field of this CertificateRequest. If the CSR has a ExtKeyUsage extension, its extended key usages must match the extended key usages in the `usages` field of this CertificateRequest.
143
145
format: byte
144
146
type: string
145
147
uid:
@@ -149,11 +151,10 @@ spec:
149
151
creation and immutable.
150
152
type: string
151
153
usages:
152
-
description: >-
153
-
Usages is the set of x509 usages that are requested for the
154
-
certificate. If usages are set they SHOULD be encoded inside
155
-
the CSR spec Defaults to `digital signature` and `key
156
-
encipherment` if not specified.
154
+
description: |-
155
+
Requested key usages and extended key usages.
156
+
NOTE: If the CSR in the `Request` field has uses the KeyUsage or ExtKeyUsage extension, these extensions must have the same values as specified here without any additional values.
157
+
If unset, defaults to `digital signature` and `key encipherment`.
157
158
items:
158
159
description: >-
159
160
KeyUsage specifies valid usage contexts for keys. See:
@@ -199,19 +200,20 @@ spec:
199
200
status:
200
201
description: >-
201
202
Status of the CertificateRequest. This is set and managed
0 commit comments