A municipal app is 'not healthy': some Pods never leave Pending while others CrashLoopBackOff. What should the admin conclude about self-healing controllers?
Select an answer to reveal the explanation.
Short Explanation
Self-healing replaces Pods that die after they were placed—it cannot invent CPU or untaint a node for something stuck Pending. Pending and CrashLoop are different problems; treat them differently.
Full Explanation
ReplicaSet/Deployment controllers reconcile replica counts for Pods that can be created and (when scheduled) restarted by kubelet. Unschedulable Pending Pods usually need capacity, selectors, taints/tolerations, or resource fixes—controllers will keep creating Pods that still cannot schedule. CrashLoopBackOff indicates start/runtime failure after scheduling, a separate failure class from Pending.