-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Issue with k8s.io/docs/tasks/extend-kubernetes/configure-multiple-schedulers/ #22394
Comments
@pparihar I'd like to understand what steps someone should take to resolve this issue If you're willing to explain further you could use the text of (eg) issue 4491 as a guide, and revise the initial description of this issue to explain the kind of work you had in mind. /triage needs-information |
Because it's not clear what is not right about that page, I propose closing this issue. I recognize that https://kubernetes.io/docs/tasks/extend-kubernetes/configure-multiple-schedulers/ does need a review and that issues including #22802 are tracking defects there. |
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. |
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. |
Thanks for the explanation but commands and YAML files are deemed to lot of errors and hence understanding of multi-schedulers is not clear.
Appreciate if you validate the entire process and update documents so that millions of people refer and understand from official git repo and kubernetes.io portal and thanks.
The text was updated successfully, but these errors were encountered: