Question

A small team currently runs containers directly on individual VMs using shell scripts. When a container crashes at night, it stays down until someone manually restarts it, causing outages. They are evaluating whether adopting a container orchestrator like Kubernetes would help. Which core orchestration capability most directly addresses their problem of crashed containers staying down?

Accepted Answer

Self-healing, where the orchestrator continuously reconciles actual state to the desired state and automatically recreates failed containers

Answer

Immutable container images built from an OCI-compliant registry that prevent containers from crashing

Answer

A service mesh that injects sidecars to encrypt traffic between the containers

Answer

Persistent volumes that retain container data across restarts so no data is lost