@@ -243,16 +243,34 @@ We expect no non-infra related flakes in the last month as a GA graduation crite
243
243
244
244
#### Alpha
245
245
246
+ - ` SelfSubjectReview ` endpoint is introduced in ` authentication.k8s.io/v1alpha1 ` API
246
247
- Feature implemented behind a feature flag
247
248
- Initial unit and integration tests completed and enabled
249
+ - Corresponding kubectl command implemented: ` kubectl alpha auth whoami `
248
250
249
251
#### Beta
250
252
251
253
- Gather feedback from users
254
+ - ` SelfSubjectReview ` is promoted to ` authentication.k8s.io/v1beta1 ` API
255
+ - Promote feature gate to Beta and make it enabled by default
256
+ - Unit tests coverage improved
257
+ - ` kubectl alpha auth whoami ` command uses ` authentication.k8s.io/v1beta1 ` API
258
+ - Fix [ documentation] ( https://kubernetes.io/docs/reference/access-authn-authz/authentication/#self-subject-review ) :
259
+ - Change API version
260
+ - Rewrite conditions to enable the feature
252
261
253
262
#### GA
254
263
255
- - Corresponding kubectl command implemented
264
+ - ` SelfSubjectReview ` is promoted to ` authentication.k8s.io/v1 ` API
265
+ - Promote feature gate to Stable
266
+ - ` kubectl alpha auth whoami ` replaced with ` kubectl auth whoami `
267
+ - ` kubectl auth whoami ` command uses ` authentication.k8s.io/v1 ` API
268
+ - An article about motivation to use this feature is added to the Kubernetes blog
269
+ - More integration and e2e tests cases
270
+ - Fix [ documentation] ( https://kubernetes.io/docs/reference/access-authn-authz/authentication/#self-subject-review ) :
271
+ - Change API version
272
+ - Rewrite conditions to enable the feature
273
+ - Change kubectl command
256
274
257
275
NOTE: Should not be a part of [ conformance tests] ( https://git.k8s.io/community/contributors/devel/sig-architecture/conformance-tests.md ) .
258
276
The fact that a user possesses a token does not necessarily imply the power to know to whom that token belongs.
@@ -263,22 +281,9 @@ The fact that a user possesses a token does not necessarily imply the power to k
263
281
264
282
###### How can this feature be enabled / disabled in a live cluster?
265
283
266
- <!--
267
- Pick one of these and delete the rest.
268
- -->
269
-
270
- - Feature gate
284
+ - [X] Feature gate (also fill in values in ` kep.yaml ` )
271
285
- Feature gate name: ` APISelfSubjectReview `
272
- - Components depending on the feature gate:
273
- - kube-apiserver
274
-
275
- ``` go
276
- FeatureSpec{
277
- Default : false ,
278
- LockToDefault : false ,
279
- PreRelease : featuregate.Alpha ,
280
- }
281
- ```
286
+ - Components depending on the feature gate: ` kube-apiserver `
282
287
283
288
###### Does enabling the feature change any default behavior?
284
289
0 commit comments