Move KEP-3542 to 1.28

Author: byako

keps/prod-readiness/sig-node/3542.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: 3542
+alpha:
+  approver: "@johnbelamaric"

keps/sig-node/3542-cri-image-pulling-with-progress-notification/README.md

@@ -175,7 +175,7 @@ updates.
 
 ## Motivation
 
-In High Performance Computing and other specialized enviroments container
+In High Performance Computing and other specialized environments container
 images often get extremely big. Pulling such images even over high speed
 links can take a lot of time, tens of minutes or more. This often results
 in a bad user experience when deploying a workload triggers pulling such
@@ -261,7 +261,7 @@ bogged down.
 #### Story 1
 
 The user is deploying an application to the k8s cluster, the Pod is being
-scheduled and creation of the Pod beginning. The only event occuring on the Pod
+scheduled and creation of the Pod beginning. The only event occurring on the Pod
 object events list is "Pulling image", with no progress indicator, or ETA.
 
 If CRI had a possility to expose the progress and / or ETA for completing the
@@ -337,7 +337,7 @@ every n. percent) or the amount of bytes downloaded which is the default one.
         PodSandboxConfig sandbox_config = 3;
         // Granularity type of the progress reports
         PullImageProgressGranularity granularity_type = 4;
-        // The interval value of the choosen granularity.
+        // The interval value of the chosen granularity.
         // For time based granularity, this is the number of seconds between reports. If time interval is 0, then report is done every 60s.
         // For percent based granularity, this is the number of percent value between reports. If percent interval is 0, then report is done every 10%
         // For the default byte based granularity, this is the number of bytes received between reports. If set to 0, then runtime will report progress as image is downloaded.

keps/sig-node/3542-cri-image-pulling-with-progress-notification/kep.yaml

@@ -6,23 +6,27 @@ authors:
 owning-sig: sig-node
 participating-sigs:
   - sig-node
-status: implementable
+status: provisional
 creation-date: 2022-09-23
-reviewers: []
-approvers: []
+reviewers:
+  - "@kubernetes/sig-node-api-reviews"
+  - "@sig-node-reviewers"
+  - "@mrunalp"
+approvers:
+  - "@sig-node-leads"
 
 # The target maturity stage in the current dev cycle for this KEP.
 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
 # worked on.
-latest-milestone: "v1.26"
+latest-milestone: "v1.28"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  alpha: "v1.26"
-  beta: "v1.27"
+  alpha: "v1.28"
+  beta: "v1.29"
   stable:
 
 # The following PRR answers are required at alpha release