Skip to content

Commit cd176a6

Browse files
authored
Merge pull request kubernetes#3379 from ruiwen-zhao/kcp
KEP-2133: add GA criteria
2 parents 6c1a3b1 + b91d648 commit cd176a6

File tree

3 files changed

+10
-3
lines changed

3 files changed

+10
-3
lines changed
Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1-
kep-number: 2053
1+
kep-number: 2133
22
beta:
33
approver: "@deads2k"
4+
stable:
5+
approver: "@deads2k"

keps/sig-node/2133-kubelet-credential-providers/README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,8 @@ can be achieved using the exec plugin.
351351

352352
#### Beta -> GA Graduation
353353

354-
TBD
354+
* existed in beta for at least 1 minor release
355+
* e2e test using an external implementation (e.g. [GCR](https://github.com/kubernetes/cloud-provider-gcp/tree/master/cmd/auth-provider-gcp)).
355356

356357
### Upgrade / Downgrade Strategy
357358

@@ -528,6 +529,8 @@ No.
528529

529530
- 2019-10-04: initial KEP introducing this functionality was merged.
530531
- 2020-11-11: PR introducing this feature at alpha stage was merged https://github.com/kubernetes/kubernetes/pull/94196
532+
- 2021-07-02: PR improving concurrency and cache for kubelet credential provider was merged https://github.com/kubernetes/kubernetes/pull/102168
533+
- 2021-09-27: PR adding metrics for kubelet credential provider was merged https://github.com/kubernetes/kubernetes/pull/102802
531534

532535
## Drawbacks
533536

keps/sig-node/2133-kubelet-credential-providers/kep.yaml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@ title: Kubelet Credential Providers
22
kep-number: 2133
33
authors:
44
- "@andrewsykim"
5+
- "@ruiwen-zhao"
56
owning-sig: sig-node
67
participating-sigs:
78
- sig-auth
@@ -27,12 +28,13 @@ stage: beta
2728
# The most recent milestone for which work toward delivery of this KEP has been
2829
# done. This can be the current (upcoming) milestone, if it is being actively
2930
# worked on.
30-
latest-milestone: "v1.24"
31+
latest-milestone: "v1.25"
3132

3233
# The milestone at which this feature was, or is targeted to be, at each stage.
3334
milestone:
3435
alpha: "v1.20"
3536
beta: "v1.24"
37+
stable: "v1.25"
3638

3739
# The following PRR answers are required at alpha release
3840
# List the feature gate name and the components for which it must be enabled

0 commit comments

Comments
 (0)