From 144ec1bb9a8338dd58e6ffb3edb6a8687e478732 Mon Sep 17 00:00:00 2001 From: wojtekt Date: Mon, 29 Nov 2021 16:46:04 +0100 Subject: [PATCH] Update Efficient Watch Resumption KEP to Stable --- keps/prod-readiness/sig-api-machinery/1904.yaml | 2 ++ .../1904-efficient-watch-resumption/README.md | 4 ++-- .../1904-efficient-watch-resumption/kep.yaml | 6 +++--- 3 files changed, 7 insertions(+), 5 deletions(-) diff --git a/keps/prod-readiness/sig-api-machinery/1904.yaml b/keps/prod-readiness/sig-api-machinery/1904.yaml index 58e7205fd90..db7cf84a894 100644 --- a/keps/prod-readiness/sig-api-machinery/1904.yaml +++ b/keps/prod-readiness/sig-api-machinery/1904.yaml @@ -1,3 +1,5 @@ kep-number: 1904 beta: approver: "@deads2k" +stable: + approver: "@deads2k" diff --git a/keps/sig-api-machinery/1904-efficient-watch-resumption/README.md b/keps/sig-api-machinery/1904-efficient-watch-resumption/README.md index 174b08fe176..f68f4ea6bf0 100644 --- a/keps/sig-api-machinery/1904-efficient-watch-resumption/README.md +++ b/keps/sig-api-machinery/1904-efficient-watch-resumption/README.md @@ -300,8 +300,8 @@ Alpha should provide basic functionality covered with tests described above. #### Beta -> GA Graduation - Enabled in Beta for at least two releases without complaints -- Rolling-upgrade of kube-apiservers in 5k-node cluster test is - automated and running periodically. +- Benefits of the feature during rolling upgrade of kube-apiserver at scale + (thousands of nodes) proven in production ### Upgrade / Downgrade Strategy diff --git a/keps/sig-api-machinery/1904-efficient-watch-resumption/kep.yaml b/keps/sig-api-machinery/1904-efficient-watch-resumption/kep.yaml index 6e5d9fc0b62..a88fa2b19fd 100644 --- a/keps/sig-api-machinery/1904-efficient-watch-resumption/kep.yaml +++ b/keps/sig-api-machinery/1904-efficient-watch-resumption/kep.yaml @@ -19,18 +19,18 @@ see-also: replaces: # The target maturity stage in the current dev cycle for this KEP. -stage: beta +stage: stable # The most recent milestone for which work toward delivery of this KEP has been # done. This can be the current (upcoming) milestone, if it is being actively # worked on. -latest-milestone: "v1.21" +latest-milestone: "v1.24" # The milestone at which this feature was, or is targeted to be, at each stage. milestone: alpha: "v1.20" beta: "v1.21" - stable: "v1.23" + stable: "v1.24" # The following PRR answers are required at alpha release # List the feature gate name and the components for which it must be enabled