Feat: graduate kube-scheduler component config to GA with some some details updated.

Signed-off-by: kerthcet <[email protected]>

Author: kerthcet

keps/prod-readiness/sig-scheduling/785.yaml

@@ -1,3 +1,5 @@
 kep-number: 785
 beta:
   approver: "@wojtek-t"
+stable:
+  approver: "@wojtek-t"

keps/sig-scheduling/785-scheduler-component-config-api/README.md

@@ -228,6 +228,12 @@ N/A
   When `v1` gets introduced:
   - Mark `v1beta2` as deprecated.
 
+* **Is the rollout accompanied by any deprecations and/or removals of features, APIs, fields of API types, flags, etc.?**
+
+  Yes, when `v1` gets introduced, we'll mark `v1beta2` as deprecated, and
+  remove the support of `v1beta2` in 1.26.
+
+
 ### Monitoring requirements
 
 * **How can an operator determine if the feature is in use by workloads?**
@@ -252,6 +258,18 @@ N/A
 
   N/A.
 
+* **What are the reasonable SLOs (Service Level Objectives) for the enhancement?**
+
+  N/A
+
+* **What are the SLIs (Service Level Indicators) an operator can use to determine the health of the service?**
+
+  N/A
+
+* **Are there any missing metrics that would be useful to have to improve observability of this feature?**
+
+  N/A
+
 ### Dependencies
 
 * **Does this feature depend on any specific services running in the cluster?**

keps/sig-scheduling/785-scheduler-component-config-api/kep.yaml

@@ -5,7 +5,7 @@ authors:
 owning-sig: sig-scheduling
 participating-sigs:
   - sig-architecture
-status: implementable
+status: implemented
 creation-date: 2020-05-08
 reviewers:
   - "@Huang-Wei"
@@ -17,7 +17,8 @@ prr-approvers:
 see-also:
   - "/keps/sig-scheduling/1451-multi-scheduling-profiles"
   - "/keps/sig-scheduling/2458-node-resource-score-strategy"
-stage: beta
-latest-milestone: "v1.23"
+stage: stable
+latest-milestone: "v1.25"
 milestone:
   beta: "v1.19"
+  stable: "v1.25"