Add Scheduling Configuration reference doc

Signed-off-by: Aldo Culquicondor <[email protected]>

content/en/docs/reference/_index.md

@@ -46,7 +46,7 @@ client libraries:
 * [kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/) - Can do simple TCP/UDP stream forwarding or round-robin TCP/UDP forwarding across a set of back-ends.
 * [kube-scheduler](/docs/reference/command-line-tools-reference/kube-scheduler/) - Scheduler that manages availability, performance, and capacity.
   * [kube-scheduler Policies](/docs/reference/scheduling/policies)
-  * [kube-scheduler Profiles](/docs/reference/scheduling/profiles)
+  * [kube-scheduler Profiles](/docs/reference/scheduling/config#profiles)
 
 ## Design Docs
 

content/en/docs/reference/scheduling/profiles.md → content/en/docs/reference/scheduling/config.md

@@ -1,9 +1,17 @@
 ---
-title: Scheduling Profiles
+title: Scheduling Configuration
 content_template: templates/concept
 weight: 20
 ---
 
+## What is new
+
+- `BindTimeoutSeconds` field in scheduler `KubeSchedulerConfiguration` is removed in v1beta1 version, please configure it via plugin args for `VolumeBinding`.
+- `v1beta1` Scheduler `Extender` encoding is now strict, its `HTTPTimeout` is `metav1.Duration` and `enableHttps` is renamed to `enableHTTPS`.
+- `RequestedToCapacityRatioArgs` decoding is now strict
+
+## Profiles
+
 {{% capture overview %}}
 
 {{< feature-state for_k8s_version="v1.18" state="alpha" >}}
@@ -24,7 +32,7 @@ The `v1alpha2` API allows you to configure kube-scheduler to run
 
 {{% capture body %}}
 
-## Extension points
+### Extension points
 
 Scheduling happens in a series of stages that are exposed through the following
 extension points:
@@ -54,7 +62,7 @@ extension points:
 1. `UnReserve`: This is an informational extension point that is called if
    a Pod is rejected after being reserved and put on hold by a `Permit` plugin.
 
-## Scheduling plugins
+### Scheduling plugins
 
 The following plugins, enabled by default, implement one or more of these
 extension points: