Skip to content

Update kube-scheduler doc to reflect Scheduling Policy deprecation #56549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Jbansal2 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update kube-scheduler doc to reflect Scheduling Policy deprecation #56549

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions content/en/docs/concepts/scheduling-eviction/kube-scheduler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,11 +75,12 @@ Finally, kube-scheduler assigns the Pod to the Node with the highest ranking.
If there is more than one node with equal scores, kube-scheduler selects
one of these at random.

There are two supported ways to configure the filtering and scoring behavior
of the scheduler:
You can configure the filtering and scoring behavior of the scheduler using
[Scheduling Profiles](/docs/reference/scheduling/config/#profiles). Scheduling Profiles allow you to configure Plugins that implement different scheduling stages, including: `QueueSort`, `Filter`, `Score`, `Bind`, `Reserve`, `Permit`, and others. You can also configure the kube-scheduler to run different profiles.

1. [Scheduling Policies](/docs/reference/scheduling/policies) allow you to configure _Predicates_ for filtering and _Priorities_ for scoring.
1. [Scheduling Profiles](/docs/reference/scheduling/config/#profiles) allow you to configure Plugins that implement different scheduling stages, including: `QueueSort`, `Filter`, `Score`, `Bind`, `Reserve`, `Permit`, and others. You can also configure the kube-scheduler to run different profiles.
{{< note >}}
Before Kubernetes v1.23, [Scheduling Policies](/docs/reference/scheduling/policies) were used to configure _Predicates_ for filtering and _Priorities_ for scoring. Scheduling Policies are deprecated and are no longer supported since v1.23.

@lmktfy lmktfy Jul 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this true? Often things that are deprecated do remain supported, sometimes for several minor releases.

@Jbansal2 Jbansal2 Jul 21, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. I based this wording on the existing Scheduling Policies documentation, which states:

"This scheduling policy is not supported since Kubernetes v1.23."

Reference: https://kubernetes.io/docs/reference/scheduling/policies/

My intention was to keep the kube-scheduler documentation consistent with the existing documentation. I'm happy to adjust the wording if you think that would make it clearer.

{{< /note >}}

## {{% heading "whatsnext" %}}

Expand Down