Bird
0
0

After draining a node and upgrading its kubelet, what is the expected node status when you run kubectl get nodes?

medium📝 Command Output Q4 of 15
Kubernetes - Production Best Practices
After draining a node and upgrading its kubelet, what is the expected node status when you run kubectl get nodes?
AThe node is deleted from the cluster
BThe node shows as Ready after rejoining the cluster
CThe node remains in NotReady state permanently
DThe node shows as SchedulingDisabled but Ready
Step-by-Step Solution
Solution:
  1. Step 1: Understand node upgrade lifecycle

    After upgrade and restart, node rejoins cluster and becomes Ready.
  2. Step 2: Analyze node status options

    Only The node shows as Ready after rejoining the cluster correctly describes node returning to Ready state after upgrade.
  3. Final Answer:

    The node shows as Ready after rejoining the cluster -> Option B
  4. Quick Check:

    Node status after upgrade = Ready [OK]
Quick Trick: Node returns to Ready after successful upgrade [OK]
Common Mistakes:
  • Expecting node to stay NotReady
  • Thinking node is deleted
  • Confusing SchedulingDisabled with Ready

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes