A municipal parking citation API declares three replicas on OKE. One replica’s process exits unexpectedly. What does orchestration self-healing do so the declared count stays true?
Select an answer to reveal the explanation.
Short Explanation
Self-heal is like a spare tire that mounts itself. When a replica dies, the orchestrator starts another so the promised count is true again. Waiting for someone to SSH and restart is not self-healing.
Full Explanation
Orchestration compares desired state to actual state. If a Pod or process exits or a worker disappears, controllers create a replacement so the declared replica count remains satisfied. Manual SSH restarts and alarm-only responses are operational workarounds, not the self-heal mechanism. Changing desired count to zero would intentionally shrink capacity.