Open aaronkjones opened 7 months ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/retitle Missing explanation on parallel multi-node draining in "Safely Drain a Node" page /language en
/sig node
It's not a bug but an improvement request for more explanation /remove-kind bug /kind feature
/assign
Raised PR in #45485
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
This is a Bug Report
Problem:
The page at
docs/tasks/administer-cluster/safely-drain-node.md
claims, "The kubectl drain command should only be issued to a single node at a time.", but does not explain further. Why is issuing the kubectl drain command discouraged when targeting more than one node at a time?Proposed Solution:
A more detailed explanation should be provided.
Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/