Library Deployments no longer create or heal pods after replica changes, while existing running pods keep serving. Which component is most likely down?
Select an answer to reveal the explanation.
Short Explanation
Controllers are the building's autopilot: without kube-controller-manager, desired replica counts stop getting fixed even though today's running pods may still hum along. Scale or heal changes just sit there.
Full Explanation
kube-controller-manager hosts controllers that reconcile Deployments, ReplicaSets, and other objects toward desired state. If it is unavailable, replica changes and self-healing stop while already-running pods can continue. kube-proxy programs Service rules, CoreDNS provides cluster DNS, and metrics-server supplies resource metrics—none of them replace Deployment reconciliation.