ARTICLE · Systems
Kubernetes
Kubernetes repeatedly compares the system you asked for with the system that is actually running, then works to reduce the difference.
Kubernetes
YouTube stays disconnected until you choose to load this player. Loading connects to Google/YouTube, which receives your IP address and may use cookies or browser storage.
An orchestra metaphor fits orchestration because coordination is the subject. Having excellent musicians does not tell them when to enter, who replaces an absent player, or how the audience finds the performance. Likewise, containerizing an application does not decide how many instances should run or what happens when a machine disappears.
Kubernetes lets you describe desired state. If a workload should have three replicas and only two are available, controllers work toward restoring the intended count. That continuing reconciliation is a better mental model than “a command that starts my containers.”
A replacement is useful only if it is ready#
Starting another process is not the same as making it ready to serve traffic. It may still be loading configuration or connecting to dependencies. Health and readiness checks help distinguish a process that exists from one that should receive requests.
The application still owns its behavior. Three replicas can repeat the same bug, exhaust the same database, or disagree about files stored on their local disks. Orchestration cannot supply an absent data model or make an unsafe operation safe to retry.
For a small project, learning to deploy and recover one service is already valuable. Add orchestration when the coordination problem justifies it. You will then recognize the work Kubernetes performs instead of mistaking a large configuration directory for evidence that your application is reliable.
See also