Updating Windows HostProcess container KEP for v1.22 alpha release

Signed-off-by: Mark Rossetti <marosset@microsoft.com>

keps/sig-windows/1981-windows-privileged-container-support/README.md

@@ -142,7 +142,7 @@ checklist items _must_ be updated for the enhancement to be released.
 Items marked with (R) are required *prior to targeting to a milestone / release*.
 
 - [X] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
-- [ ] (R) KEP approvers have approved the KEP status as `implementable`
+- [X] (R) KEP approvers have approved the KEP status as `implementable`
 - [X] (R) Design details are appropriately documented
 - [X] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
 - [X] (R) Graduation criteria is in place
@@ -751,17 +751,17 @@ in back-to-back releases.
 Alpha
 
 - Version of containerd: Target v1.5
-- Version of Kubernetes: Target 1.21
-- OS support: 1809/Windows 2019 LTSC and all future versions of Windows Server
+- Version of Kubernetes: Target 1.22
+- OS support: Windows 2019 LTSC and all future versions of Windows Server
 - Alpha Feature Gate for passing privileged flag **or** annotations to CRI calls.
 
 Beta
 
 - Go through PSP Linux test (e2e: validation & conformance) and make them relevant for Windows (which apply, which don't and where we need to write new tests).
 - Provide guidance similar to Pod Security Standards for Windows privileged containers
 - Containerd: v1.5
-- Kubernetes Target 1.22 or later
-- OS support: 1809/Windows 2019 LTSC and all future versions of Windows Server
+- Kubernetes Target 1.23 or later
+- OS support: Windows 2019 LTSC and all future versions of Windows Server
 - Beta Feature Gate for passing privilege flag to CRI
 - Extensive documentation around `HostProcess` containers on https://kubernetes.io/
   - Includes clarification around disk limits mentioned in [Resource Limits](#resource-limits)

keps/sig-windows/1981-windows-privileged-container-support/kep.yaml

@@ -28,11 +28,11 @@ 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.21"
+latest-milestone: "v1.22"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
-  alpha: "v1.21"
+  alpha: "v1.22"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled