KEP-4033: target to alpha for 1.28

Signed-off-by: Peter Hunt <pehunt@redhat.com>

Author: haircommander

keps/prod-readiness/sig-node/4033.yaml

@@ -2,5 +2,5 @@
 # "prod-readiness-approvers" group
 # of http://git.k8s.io/enhancements/OWNERS_ALIASES
 kep-number: 4033
-beta:
+alpha:
   approver: "@johnbelamaric"

keps/sig-node/4033-group-driver-detection-over-cri/README.md

@@ -97,6 +97,7 @@ tags, and then generate with `hack/update-toc.sh`.
       - [Integration tests](#integration-tests)
       - [e2e tests](#e2e-tests)
   - [Graduation Criteria](#graduation-criteria)
+    - [Alpha](#alpha)
     - [Beta](#beta)
     - [GA](#ga)
   - [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
@@ -436,17 +437,23 @@ in back-to-back releases.
 - Deprecate the flag
 -->
 
-The feature is targeting directly to beta, with the feature gate enabled by
-default.
+#### Alpha
+
+- [ ] Feature implemented behind a feature flag, fallback to old behavior if flag is enabled but runtime support not present.
+- [ ] Initial unit tests completed and enabled
+
 
 #### Beta
 
 - [ ] Feature implemented, with the feature gate enabled by default.
+- [ ] Released versions of CRI-O and containerd runtime implementations support the feature
+- [ ] Drop fallback to old behavior. CRI implementations expected to have support.
 
 #### GA
 
-- [ ] released versions of CRI-O and containerd runtime implementations support the feature
 - [ ] No bugs reported in the previous cycle.
+- [ ] Remove fallback behavior
+- [ ] Remove feature gate
 
 ### Upgrade / Downgrade Strategy
 
@@ -462,6 +469,11 @@ enhancement:
   cluster required to make on upgrade, in order to make use of the enhancement?
 -->
 
+The fallback behavior specified in alpha will prevent the majority of regressions, as Kubelet will choose a cgroup driver,
+same as it used to before this KEP, even when the feature gate is on.
+
+The feature gate is another layer of protection, requiring admins to specifically opt-into this behavior.
+
 ### Version Skew Strategy
 
 <!--
@@ -544,7 +556,7 @@ automations, so be extremely careful here.
 Yes. If/when the runtime is updated to a version that supports this, kubelet
 will ignore the cgroupDriver config option/flag. However, this change in
 behavior should not cause any breakages (on the contrary, it should fix
-scenarios where the kubelet `--cgorup-driver` setting is incorrectly
+scenarios where the kubelet `--cgroup-driver` setting is incorrectly
 configured). With old versions of the container runtimes (that don't support
 the new field in the CRI API) the default behavior is not changed.
 

keps/sig-node/4033-group-driver-detection-over-cri/kep.yaml

@@ -17,7 +17,7 @@ see-also: []
 replaces: []
 
 # The target maturity stage in the current dev cycle for this KEP.
-stage: beta
+stage: alpha
 
 # 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
@@ -26,8 +26,9 @@ latest-milestone: "v1.28"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  beta: "v1.28"
-  stable: "v1.yy"
+  alpha: "v1.28"
+  beta: "v1.yy"
+  stable: "v1.zz"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled