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: content/en/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,8 +67,6 @@ CertificateSigningRequestSpec contains the certificate request.
67
67
68
68
-**request** ([]byte), required
69
69
70
-
*Atomic: will be replaced during a merge*
71
-
72
70
request contains an x509 certificate signing request encoded in a "CERTIFICATE REQUEST" PEM block. When serialized as JSON or YAML, the data is additionally base64-encoded.
73
71
74
72
-**signerName** (string), required
@@ -159,8 +157,6 @@ CertificateSigningRequestStatus contains conditions used to indicate approved/de
159
157
160
158
-**certificate** ([]byte)
161
159
162
-
*Atomic: will be replaced during a merge*
163
-
164
160
certificate is populated with an issued certificate by the signer after an Approved condition is present. This field is set via the /status subresource. Once populated, this field is immutable.
165
161
166
162
If the certificate signing request is denied, a condition of type "Denied" is added and this field remains empty. If the signer cannot issue the certificate, a condition of type "Failed" is added and this field remains empty.
status contains the issued certificate, and a standard set of conditions.
54
54
@@ -122,6 +122,14 @@ PodCertificateRequestSpec describes the certificate request. All fields are imm
122
122
123
123
The signer implementation is then free to issue a certificate with any lifetime *shorter* than MaxExpirationSeconds, but no shorter than 3600 seconds (1 hour). This constraint is enforced by kube-apiserver. `kubernetes.io` signers will never issue certificates with a lifetime longer than 24 hours.
unverifiedUserAnnotations allow pod authors to pass additional information to the signer implementation. Kubernetes does not restrict or validate this metadata in any way.
128
+
129
+
Entries are subject to the same validation as object metadata annotations, with the addition that all keys must be domain-prefixed. No restrictions are placed on values, except an overall size limitation on the entire field.
130
+
131
+
Signers should document the keys and values they support. Signers should deny requests that contain keys they do not recognize.
132
+
125
133
126
134
127
135
@@ -220,7 +228,7 @@ PodCertificateRequestList is a collection of PodCertificateRequest objects
220
228
221
229
<hr>
222
230
223
-
-**apiVersion**: certificates.k8s.io/v1alpha1
231
+
-**apiVersion**: certificates.k8s.io/v1beta1
224
232
225
233
226
234
-**kind**: PodCertificateRequestList
@@ -230,7 +238,7 @@ PodCertificateRequestList is a collection of PodCertificateRequest objects
Copy file name to clipboardExpand all lines: content/en/docs/reference/kubernetes-api/cluster-resources/runtime-class-v1.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,11 +84,13 @@ RuntimeClass defines a class of container runtime supported in the cluster. The
84
84
85
85
-**scheduling.tolerations.operator** (string)
86
86
87
-
Operator represents a key's relationship to the value. Valid operators are Existsand Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
87
+
Operator represents a key's relationship to the value. Valid operators are Exists, Equal, Lt, and Gt. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category. Lt and Gt perform numeric comparisons (requires feature gate TaintTolerationComparisonOperators).
Copy file name to clipboardExpand all lines: content/en/docs/reference/kubernetes-api/common-definitions/status.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,8 +40,6 @@ Status is a return value for calls that don't return other objects.
40
40
41
41
-**details** (StatusDetails)
42
42
43
-
*Atomic: will be replaced during a merge*
44
-
45
43
Extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.
Copy file name to clipboardExpand all lines: content/en/docs/reference/kubernetes-api/config-and-storage-resources/csi-driver-v1.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,18 @@ CSIDriverSpec is the specification of a CSIDriver.
107
107
108
108
Default is "false".
109
109
110
+
-**serviceAccountTokenInSecrets** (boolean)
111
+
112
+
serviceAccountTokenInSecrets is an opt-in for CSI drivers to indicate that service account tokens should be passed via the Secrets field in NodePublishVolumeRequest instead of the VolumeContext field. The CSI specification provides a dedicated Secrets field for sensitive information like tokens, which is the appropriate mechanism for handling credentials. This addresses security concerns where sensitive tokens were being logged as part of volume context.
113
+
114
+
When "true", kubelet will pass the tokens only in the Secrets field with the key "csi.storage.k8s.io/serviceAccount.tokens". The CSI driver must be updated to read tokens from the Secrets field instead of VolumeContext.
115
+
116
+
When "false" or not set, kubelet will pass the tokens in VolumeContext with the key "csi.storage.k8s.io/serviceAccount.tokens" (existing behavior). This maintains backward compatibility with existing CSI drivers.
117
+
118
+
This field can only be set when TokenRequests is configured. The API server will reject CSIDriver specs that set this field without TokenRequests.
119
+
120
+
Default behavior if unset is to pass tokens in the VolumeContext field.
121
+
110
122
-**storageCapacity** (boolean)
111
123
112
124
storageCapacity indicates that the CSI volume driver wants pod scheduling to consider the storage capacity that the driver deployment will report by creating CSIStorageCapacity objects with capacity information, if set to true.
0 commit comments