Skip to content

Kubernetes Scheduler refers to obsolete(?) Scheduling policies #45122

Open
@Etua

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    language/enIssues or PRs related to English languagelifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/schedulingCategorizes an issue or PR as relevant to SIG Scheduling.

    Type

    No type

    Projects

    Status

    Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions