Address reviewer comments for v1.30

Author: Jeffwan

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

@@ -0,0 +1,6 @@
+# The KEP must have an approver from the
+# "prod-readiness-approvers" group
+# of http://git.k8s.io/enhancements/OWNERS_ALIASES
+kep-number: 4176
+alpha:
+  approver: "@jpbetz"

keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/README.md

@@ -501,7 +501,7 @@ If we reactivate the feature after a rollback, the outcome remains unchanged. Cu
 
 ###### Are there any tests for feature enablement/disablement?
 
-A dedicated e2e test will validate the preservation of the default behavior when the feature gate is turned off or when the feature is unused. This will be conducted through two distinct test scenarios.
+A dedicated e2e test will validate the preservation of the default behavior when the feature gate is turned off, when the feature is unused, when `pread-physical-cpus-preferred` turns off but `CPUManagerPolicyAlphaOptions` is disabled. This will be conducted through three distinct test scenarios.
 
 <!--
 The e2e framework does not currently support enabling or disabling feature
@@ -666,7 +666,7 @@ and creating new ones, as well as about cluster-level services (e.g. DNS):
       - Impact of its degraded performance or high-error rates on the feature:
 -->
 
-This applies to any machines with hyper-threading enabled.
+No. It doesn't rely on other Kubernetes components.
 
 ### Scalability
 

keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/kep.yaml

@@ -26,9 +26,9 @@ latest-milestone: "v1.29"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  alpha: "v1.29"
-  beta: "v1.30"
-  stable: "v1.32"
+  alpha: "v1.30"
+  beta: "v1.31"
+  stable: "v1.33"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled