Operators declare three healthy replicas of a licensing API image. What posture distinguishes an orchestrator from a human start/stop runbook?
Select an answer to reveal the explanation.
Short Explanation
You declare three healthy replicas; the orchestrator keeps comparing the world to that wish and fixes the drift. A human runbook of start/stop commands is the opposite posture.
Full Explanation
Orchestrators implement continuous reconciliation: the declared desired state (for example three healthy replicas of an image) is compared to cluster reality, and the control loop creates, replaces, or retires instances until they match. Imperative human runbooks of start and stop commands do not provide that ongoing loop. This extends the declarative-API pillar with the orchestrator as the actor.