Introduce v1beta3 api

Author: ravisantoshgudimetla

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

@@ -47,7 +47,7 @@
 
 The kube-scheduler configuration API `kubescheduler.config.k8s.io` was in alpha
 for several releases. We graduated it to beta in 1.19 as `v1beta1`. In 1.22,
-we introduced `v1beta2`.
+we introduced `v1beta2`. In 1.23, we plan to introduce `v1beta3`
 
 ## Motivation
 
@@ -70,7 +70,7 @@ usage.
 
 - Introduce `kubescheduler.config.k8s.io/v1beta1` as a copy of
 `kubescheduler.config.k8s.io/v1alpha2` with minimal cleanup changes.
-- Iterate the API in `kubescheduler.config.k8s.io/v1beta2`, based on learnings.
+- Iterate the API in `kubescheduler.config.k8s.io/v1beta3`, based on learnings.
 - Use the newly created API objects to build the default configuration for kube-scheduler.
 
 ### Non-Goals
@@ -97,6 +97,14 @@ The second iteration, `kubescheduler.config.k8s.io/v1beta2`, includes the follow
     - `RequestedToCapacityRatio` (in favor of `NodeResourcesFit` plugin with a `RequestedToCapacityRatio` scoring strategy)
   - Cleanup of validation hacks.
 
+The third iteration, `kubescheduler.config.k8s.io/v1beta3`, includes the following changes:
+  - Change the weights of the following user configurable plugins.
+    - `InterPodAffinity` to 2
+    - `NodeAffinity` to 2
+    - `TaintToleration` to 3 as the usage of node tainting to group nodes in the cluster is increasing for many user workloads
+
+The main reason for increasing the weights of the above plugins is conflict with other plugins like image locality, utilization.
+More information can be found [here](https://github.com/kubernetes/kubernetes/issues/88174)     
 ### Risks and Mitigations
 
 The major risk is around the removal of the `unreserve` extension point.
@@ -121,6 +129,7 @@ This will be documented in https://kubernetes.io/docs/reference/scheduling/profi
 - [x] Tests for `RequestedToCapacityRatioArgs` that: (1) fail to pass with
   bad casing and (2) get encoded with lower case.
 - [x] Tests for parsing, conversion, defaulting and validation.
+- [] Tests which assert predictability of node assignment with increased weights.
 
 ### Graduation Criteria
 
@@ -136,7 +145,7 @@ This will be documented in https://kubernetes.io/docs/reference/scheduling/profi
 
 ### Upgrade/Downgrade Strategy
 
-Users are able to use the `v1beta1` or `v1beta2` APIs. Since they only affect
+Users are able to use the `v1beta1`, `v1beta2`, `v1beta3` APIs. Since they only affect
 the configuration of the scheduler, there is no impact to running workloads.
 
 The default configurations preserve the behavior of the scheduler.
@@ -172,7 +181,7 @@ N/A
 
   The e2e framework does not currently support changing configuration files.
 
-  There are intensive unit tests for both API versions.
+  There are intensive unit tests for all the API versions.
 
 ### Rollout, Upgrade and Rollback Planning
 
@@ -203,6 +212,9 @@ N/A
   - Some plugins are disabled. They continue to work in `v1beta1`; if used,
     kube-scheduler logs a Warning.
 
+  When `v1beta3` gets introduced:
+  - No changes to plugins enabled by default. Only their weights would change.  
+
 ### Monitoring requirements
 
 * **How can an operator determine if the feature is in use by workloads?**
@@ -283,4 +295,5 @@ N/A
 - 2020-05-08: KEP for beta graduation sent for review, including motivation,
   proposal, risks, test plan and graduation criteria.
 - 2020-05-13: KEP updated to remove v1alpha2 support.
-- 2021-07-08: Introducing `v1beta2`
+- 2021-07-08: Introducing `v1beta2`
+- 2021-08-06: Introducing `v1beta3` 

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

@@ -18,6 +18,6 @@ see-also:
   - "/keps/sig-scheduling/1451-multi-scheduling-profiles"
   - "/keps/sig-scheduling/2458-node-resource-score-strategy"
 stage: beta
-latest-milestone: "v1.22"
+latest-milestone: "v1.23"
 milestone:
   beta: "v1.19"