Update version skew strategy and use original beta/ga milestones

Author: vinaykul

keps/sig-node/1287-in-place-update-pod-resources/README.md

@@ -695,8 +695,15 @@ Downgrade involves doing the above in reverse.
 
 ### Version Skew Strategy
 Kubelet and the CRI runtime versions are expected to match so we don't have to worry about.
+
 Previous versions of clients that are unaware of the new ResizePolicy fields would set them
-to nil. API server mutates such updates by copying non-nil values from old Pod to current Pod
+to nil. API server mutates such updates by copying non-nil values from old Pod to the current
+Pod.
+
+A previous version of kubelet interprets mutation to Pod Resources as a Container definition
+change and will restart the container with the new Resources. This could lead to Node resource
+over-subscription. In order to address this, the feature-gate will remain default false for
+atleast two versions after the initial release that carries it.
 
 ## Production Readiness Review Questionnaire
 

keps/sig-node/1287-in-place-update-pod-resources/kep.yaml

@@ -35,8 +35,8 @@ latest-milestone: "v1.22"
 
 milestone:
   alpha: "v1.22"
-  beta: "v1.24"
-  stable: "v1.26"
+  beta: "v1.23"
+  stable: "v1.25"
 
 feature-gates:
   - name: InPlacePodVerticalScaling

keps/sig-node/2273-kubelet-container-resources-cri-api-changes/kep.yaml

@@ -26,8 +26,8 @@ latest-milestone: "v1.22"
 
 milestone:
   alpha: "v1.22"
-  beta: "v1.24"
-  stable: "v1.26"
+  beta: "v1.23"
+  stable: "v1.25"
 
 feature-gates:
   - name: InPlacePodVerticalScaling