-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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.
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
Deprecated flags are recommended on k8s.io/docs/reference/scheduling/policies/ #21051
Comments
It sounds like it might be OK to revise https://kubernetes.io/docs/reference/scheduling/policies/ to mark the whole topic as deprecated. That's appropriate if this kind of configuration is indeed deprecated; I have not checked that. |
/sig scheduling |
It looks like the topic isn't entirely deprecated, the way that the configuration is provided has just been changed radically. Something to do with a shift to "ComponentConfig". See here for the new approach. And here for an example config which shows how to set the policies via a file or ConfigMap, plus an example of how these policies are configured. I haven't been able to find proper documentation for any of this yet. The Is there some general way of getting the cluster itself to tell me what format it expects and what plugins are available? I haven't tried any of this out yet. |
Maybe the policy format is still the one linked from the existing documentation and the available predicates and priorities are still the ones documented. If that is the case, the only change needs to be adding documentation for how to refer to the policy config using |
According to https://pkg.go.dev/k8s.io/kubernetes/pkg/scheduler/apis/config?tab=doc#KubeSchedulerConfiguration That would resolve this issue. It still leaves me working on how to get the scheduler configured using the new approach. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Likewise, all I really want to do is enable MostRequestedPriority but I'm at a loss on what the right way to do this is without using these "deprecated" arguments/methods |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is a Bug Report
Problem:
The documentation recommends configuring
kube-scheduler
with--policy-config-file
or--policy-configmap
which are deprecated.Proposed Solution:
Replace the instructions with a solution which is not deprecated. I'm haven't yet been able to find out what the recommended solution is.
Alternative solution: If there is no viable recommended way to set the policy config, then open a ticket against
kube-scheduler
to remove the "DEPRECATED" marking.Page to Update:
https://kubernetes.io/docs/reference/scheduling/policies/
The text was updated successfully, but these errors were encountered: