From d01d3c9182ff25ea600318ebd676ac680e650d85 Mon Sep 17 00:00:00 2001
From: Jitendra Bansal <146943450+Jbansal2@users.noreply.github.com>
Date: Mon, 20 Jul 2026 13:50:23 +0530
Subject: [PATCH] Update kube-scheduler doc to reflect Scheduling Policy
 deprecation

---
 .../docs/concepts/scheduling-eviction/kube-scheduler.md  | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/scheduling-eviction/kube-scheduler.md b/content/en/docs/concepts/scheduling-eviction/kube-scheduler.md
index 313d56fe34da7..c554ef5e9151c 100644
--- a/content/en/docs/concepts/scheduling-eviction/kube-scheduler.md
+++ b/content/en/docs/concepts/scheduling-eviction/kube-scheduler.md
@@ -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.
+{{< /note >}}
 
 ## {{% heading "whatsnext" %}}