Add StorageCapacityScoring feature gate documents

The VolumeCapacityPriority feature gate is replaced by the StorageCapacityScoring feature gate.

Author: cupnes

content/en/docs/concepts/scheduling-eviction/scheduling-framework.md

@@ -130,6 +130,18 @@ defined range of integers representing the minimum and maximum scores. After the
 [NormalizeScore](#normalize-scoring) phase, the scheduler will combine node
 scores from all plugins according to the configured plugin weights.
 
+#### Capacity scoring {#scoring-capacity}
+
+{{< feature-state feature_gate_name="StorageCapacityScoring" >}}
+
+The feature gate `VolumeCapacityPriority` was used in v1.32 to support storage that are
+statically provisioned. Starting from v1.33, the new feature gate `StorageCapacityScoring`
+replaces the old `VolumeCapacityPriority` gate with added support to dynamically provisioned storage.
+When `StorageCapacityScoring` is enabled, the VolumeBinding plugin in the kube-scheduler is extended
+to score Nodes based on the storage capacity on each of them.
+This feature is applicable to CSI volumes that supported [Storage Capacity](/docs/concepts/storage/storage-capacity/),
+including local storage backed by a CSI driver.
+
 ### NormalizeScore {#normalize-scoring}
 
 These plugins are used to modify scores before the scheduler computes a final

content/en/docs/reference/command-line-tools-reference/feature-gates/StorageCapacityScoring.md

@@ -0,0 +1,19 @@
+---
+title: StorageCapacityScoring
+content_type: feature_gate
+_build:
+ list: never
+ render: false
+
+stages:
+ - stage: alpha
+ defaultValue: false
+ fromVersion: "1.33"
+---
+The feature gate `VolumeCapacityPriority` was used in v1.32 to support storage that are
+statically provisioned. Starting from v1.33, the new feature gate `StorageCapacityScoring`
+replaces the old `VolumeCapacityPriority` gate with added support to dynamically provisioned storage.
+When `StorageCapacityScoring` is enabled, the VolumeBinding plugin in the kube-scheduler is extended
+to score Nodes based on the storage capacity on each of them.
+This feature is applicable to CSI volumes that supported [Storage Capacity](/docs/concepts/storage/storage-capacity/),
+including local storage backed by a CSI driver.

content/en/docs/reference/command-line-tools-reference/feature-gates/VolumeCapacityPriority.md

@@ -9,6 +9,9 @@ stages:
  - stage: alpha 
  defaultValue: false
  fromVersion: "1.21"
+ toVersion: "1.32"
+
+removed: true
 ---
 Enable support for prioritizing nodes in different
 topologies based on available PV capacity.

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

@@ -143,7 +143,7 @@ extension points:
  {{< glossary_tooltip text="volumes" term_id="volume" >}}.
  Extension points: `preFilter`, `filter`, `reserve`, `preBind`, `score`.
  {{< note >}}
- `score` extension point is enabled when `VolumeCapacityPriority` feature is
+ `score` extension point is enabled when `StorageCapacityScoring` feature is
  enabled. It prioritizes the smallest PVs that can fit the requested volume
  size.
  {{< /note >}}
@@ -332,14 +332,14 @@ The general hierarchy for precedence when configuring `MultiPoint` plugins is as
 3. Default plugins and their default settings
 
 To demonstrate the above hierarchy, the following example is based on these plugins:
-|Plugin|Extension Points|
-|---|---|
-|`DefaultQueueSort`|`QueueSort`|
-|`CustomQueueSort`|`QueueSort`|
-|`DefaultPlugin1`|`Score`, `Filter`|
-|`DefaultPlugin2`|`Score`|
-|`CustomPlugin1`|`Score`, `Filter`|
-|`CustomPlugin2`|`Score`, `Filter`|
+| Plugin | Extension Points |
+| ------------------ | ----------------- |
+| `DefaultQueueSort` | `QueueSort` |
+| `CustomQueueSort` | `QueueSort` |
+| `DefaultPlugin1` | `Score`, `Filter` |
+| `DefaultPlugin2` | `Score` |
+| `CustomPlugin1` | `Score`, `Filter` |
+| `CustomPlugin2` | `Score`, `Filter` |
 
 A valid sample configuration for these plugins would be: