Revision poster: why Kubernetes exists.
Use this as the one-page summary of the orientation module. Read it left to right: each question on the left is answered by a built-in mechanism on the right.
- 1Placement: the scheduler picks a node that fits.
- 2Failure: controllers notice a missing Pod and create a replacement.
- 3Discovery: Services give a stable name and address, DNS resolves it.
- 4Rollout: Deployments replace Pods gradually and can roll back.
- 5Scale: autoscalers add Pods, and nodes when Pods no longer fit.
- 6All five run on the observe, compare, act loop against your declared state.
Self-check: cover the poster and answer
- Which component answers each of the five questions?
- What are the three steps of the loop, and what does each one do?
Declare the desired state once and Kubernetes keeps it true.