Running containers directly on individual machines can make each host a special case and require hands-on configuration as the application grows. A container orchestrator such as Kubernetes schedules and monitors containers across a shared pool of machines, so teams can focus on deploying applications instead of managing each host. section 1.2 section 3.0
Describe what the deployment needs—such as the number of container instances, availability, and service networking—and the orchestrator manages where containers run. This supports multiple services on shared compute, including stateless applications, databases, and batch jobs. section 3.0
Orchestration helps teams:
- Scale applications without configuring each machine individually. section 1.2
- Spread services across failure domains to support high availability. section 1.2
- Roll out service updates by changing configuration and letting Kubernetes apply them across zones. section 1.2
Shows a Kubernetes cluster managing several services across three zones. section 1.2
