Kubernetes / Cluster Operations, Access & Incident Response
Review node workloads before planning a Kubernetes drain
Draining affects application availability, local temporary data and storage attachment. Inventory the node before initiating eviction.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl get pods -A --field-selector spec.nodeName=node01 -o wideRead the result
With authorized visibility, this lists Pods assigned to the example node. Owners, disruption budgets and local data requirements need separate inspection.
Resolve and verify
Coordinate replica health, destination capacity and persistent-volume behavior with workload owners. Use the supported reviewed drain procedure and verify recovery afterward.
Before changing production
Do not force-delete workloads or ignore disruption budgets just to complete maintenance faster.