Kubernetes Scheduler refers to obsolete(?) Scheduling policies

[Etua]

kube-scheduler.md contains this line from 2020: Scheduling Policies allow you to configure Predicates for filtering and Priorities for scoring.

However, the page it refers to says:
In Kubernetes versions before v1.23, a scheduling policy can be used to specify the predicates and priorities process. For example, you can set a scheduling policy by running kube-scheduler --policy-config-file or kube-scheduler --policy-configmap .

This scheduling policy is not supported since Kubernetes v1.23. Associated flags policy-config-file, policy-configmap, policy-configmap-namespace and use-legacy-policy-config are also not supported. Instead, use the Scheduler Configuration to achieve similar behavior.

1.23 came out in 2021, so after the line from kube-scheduler.md had been written. My best guess is, that with 1.23 it should have been updated to Scheduler Configuration page, but I'm not that familiar with the topic (that's why I read the documentation after all), and this would maybe reduce the 2 points from the original page back to 1, at least in terms of pages it refers to, so ideally someone better informed could confirm that.

[dipesh-rawat]

/language en
/sig scheduling

[niranjandarshann]

@Etua Thank you for bringing this in attention.
You are correct that there has been a change in Kubernetes versions regarding scheduling policies. With the release of Kubernetes v1.23, the scheduling policy functionality, along with associated flags such as policy-config-file, policy-configmap, policy-configmap-namespace, and use-legacy-policy-config, has been deprecated and is no longer supported.

[reylejano]

/triage accepted

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale