Promote PodOS field to GA

Author: ravisantoshgudimetla

keps/prod-readiness/sig-windows/2802.yaml

@@ -3,3 +3,5 @@ alpha:
   approver: "@deads2k"
 beta:
   approver: "@deads2k"
+stable:
+  approver: "@deads2k"

keps/sig-windows/2802-identify-windows-pods-apiserver-admission/README.md

@@ -201,6 +201,8 @@ express scheduling constraints. During the alpha, we assume there are no schedul
 
 #### Beta -> GA Graduation
 - 2 examples of end users using this field
+  - The latest version of OpenShift is using OS field in pod spec to identify pod OS and apply SCCs judiciously
+  - Racher, CAPZ plan to use this field.
 
 ### Upgrade / Downgrade Strategy
 
@@ -380,6 +382,7 @@ Disabling the `IdentifyPodOS` featuregate will help in determining the problem.
 - 2021-09-08: Initial KEP merged
 - 2021-10-29: Initial implementation PR merged
 - 2022-01-19: Graduate the feature to Beta proposed 
+- 2022-05-09: Graduate the feature to GA proposed
 
 
 ## Drawbacks

keps/sig-windows/2802-identify-windows-pods-apiserver-admission/kep.yaml

@@ -18,12 +18,12 @@ prr-approvers:
   - "@deads2k"
 creation-date: 2021-06-28
 # The target maturity stage in the current dev cycle for this KEP.
-stage: beta
+stage: stable
 
 # 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.24"
+latest-milestone: "v1.25"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone: