Kubernetes - Troubleshooting
After running
kubectl drain node-2 --ignore-daemonsets, what is the expected state of node-2?After running kubectl drain node-2 --ignore-daemonsets, what is the expected state of node-2?
medium📝 Command Output Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Understand drain command effect
The drain command marks the node unschedulable and evicts pods except daemonsets when --ignore-daemonsets is used.Step 2: Confirm node state after drain
Node-2 will be cordoned and pods evicted except daemonsets.Final Answer:
Node-2 is cordoned and all pods except daemonsets are evicted -> Option BQuick Check:
Drain = cordon + pod eviction except daemonsets [OK]
Quick Trick: Drain cordons node and evicts pods except daemonsets [OK]
Common Mistakes:
- Thinking drain deletes node
- Assuming node is uncordoned after drain
- Believing node reboots automatically
Master "Troubleshooting" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes