-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
“Safely Drain a Node” states that you need Kubernetes 1.5 or later #40453
Comments
/assign |
kubernetes 1.5 release end of life (1 October 2017) already passed so this page needs updation |
/kind bug |
I guess it is mentioned because in v1.5:
As per release page
It totally depends upon the docs and |
/retitle “Safely Drain a Node” states that you need Kubernetes 1.5 or later That statement is correct and its inclusion does not, to me, feel misleading. /priority awaiting-more-evidence |
Just to confirm the version indicates the complete functionality is not available until v1.5 is released? PDB is noted released in stable 1.21. Only confusing area is what functionality in the document is for 1.5 and what is available now? |
Try this: https://www.google.com/search?q=when+was+kubernetes+1.5+released The page does not say you need to wait for an upcoming release. I think you have misunderstood what is actually a clear statement @wsmelton. We could drop the |
/triage accepted |
/priority important-longterm |
For SIG Docs, this is only a backlog priority I think. We've other work that we'd want to prioritize. Help here is still very welcome! |
The PR #23755 improperly set the minim version to 1.5 when there is no such version.
Public link: https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/
Markdown file: https://github.com/sftim/kubernetes-website/blob/main/content/en/docs/tasks/administer-cluster/safely-drain-node.md
The text was updated successfully, but these errors were encountered: