It's in alpha and disabled by default. The `VolumeCapacityPriority` alpha feature was replaced with this, and the default behavior was changed. The `VolumeCapacityPriority` preferred a node with the least allocatable, but the `StorageCapacityScoring` preferred a node with the maximum allocatable. See [KEP-4049](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/4049-storage-capacity-scoring-of-nodes-for-dynamic-provisioning/README.md) for details. ([#128184](https://github.co...

  This allows the scheduler to handle cluster events faster with less memory.

  Specific node events include updates to taints, tolerations or allocatable.
  In-tree plugins now ignore node updates that don't modify any of these fields. ([#127220](https://github.com/kubernetes/kubernetes/pull/127220), [@sanposhiho](https://github.com/sanposhiho)) [SIG Node, Scheduling and Storage]

- The fallback behavior of the Downward API's `resourceFieldRef` field was updated to account for pod-level resources: if container-level limits were not set, pod-level limits were now used before falling back to node allocatable resources. ([#132605](https://github.com/kubernetes/kubernetes/pull/132605), [@toVersus](https://github.com/toVersus)) [SIG Node, Scheduling and Testing]

      <match value="0xCFFAEDFE" type="string" offset="0"/>
    </magic>
  </mime-type>
  <mime-type type="application/x-mach-o-object">
    <_comment>Mach-O relocatable object file</_comment>
    <magic priority="55">
      <match value="0xFEEDFACE" type="string" offset="0">
        <match value="0x00000001" type="big32" offset="12"/>
      </match>