What happened?

Followed up with @alculquicondor, VolumeBinding Score plugin is enabled only when the feature gate VolumeCapacityPriority is enabled:

However, with v1beta3 and v1, VolumeBinding Score plugin is no longer feature gated (although its underlying logic is).

What did you expect to happen?

We'd pursue disabling a plugin if the feature gate is disabled. Another thread: #113275 (comment)

How can we reproduce it (as minimally and precisely as possible)?

Run kube-scheduler using a v1beta3 or v1 config, without enabling VolumeCapacityPriority feature gate.

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)