Bird
0
0

For upgrading a Kubernetes cluster with 100 worker nodes while ensuring zero downtime, which upgrade approach is most appropriate?

hard📝 Workflow Q8 of 15
Kubernetes - Production Best Practices
For upgrading a Kubernetes cluster with 100 worker nodes while ensuring zero downtime, which upgrade approach is most appropriate?
ADelete and recreate the cluster with the new version
BUpgrade all nodes simultaneously during a maintenance window
CPerform a rolling upgrade by draining and upgrading nodes one at a time
DUpgrade only the master nodes and leave workers unchanged
Step-by-Step Solution
Solution:
  1. Step 1: Understand zero downtime requirement

    Zero downtime means workloads must remain available during upgrade.
  2. Step 2: Use rolling upgrade strategy

    Draining and upgrading nodes one at a time ensures workloads are rescheduled on healthy nodes, maintaining availability.
  3. Step 3: Avoid simultaneous upgrades

    Upgrading all nodes at once risks service disruption.
  4. Final Answer:

    Perform a rolling upgrade by draining and upgrading nodes one at a time -> Option C
  5. Quick Check:

    Rolling upgrades minimize downtime [OK]
Quick Trick: Upgrade nodes sequentially to keep workloads available [OK]
Common Mistakes:
  • Upgrading all nodes simultaneously causing downtime
  • Recreating cluster causing service interruption
  • Ignoring worker node upgrades

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes