Microservices - Orchestration with KubernetesHow can you ensure a Deployment automatically replaces unhealthy Pods to maintain service availability?AUse a Service with type LoadBalancerBIncrease the number of replicas manuallyCSet readiness and liveness probes in Pod specDDisable rolling updatesCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand probes roleLiveness and readiness probes detect unhealthy Pods so Deployment can replace them.Step 2: Evaluate other optionsIncreasing replicas doesn't replace unhealthy Pods, LoadBalancer is for traffic, disabling rolling updates is unrelated.Final Answer:Set readiness and liveness probes in Pod spec -> Option CQuick Check:Probes enable auto-replacement of unhealthy Pods [OK]Quick Trick: Use probes to detect and replace bad Pods [OK]Common Mistakes:MISTAKESThinking replicas fix unhealthy PodsConfusing Service type with health checksDisabling rolling updates to fix health
Master "Orchestration with Kubernetes" in Microservices9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepArchTryChallengeDesignRecallScale
More Microservices Quizzes Authentication and Authorization - Why security spans all services - Quiz 3easy Authentication and Authorization - Service-to-service authentication - Quiz 6medium Authentication and Authorization - Why security spans all services - Quiz 15hard Authentication and Authorization - JWT token propagation - Quiz 14medium Event-Driven Architecture - Event replay - Quiz 10hard Monitoring and Observability - Distributed tracing (Jaeger, Zipkin) - Quiz 10hard Monitoring and Observability - Dashboards (Grafana) - Quiz 4medium Orchestration with Kubernetes - Services and networking - Quiz 9hard Resilience Patterns - Bulkhead pattern - Quiz 10hard Service Mesh - Istio overview - Quiz 12easy