A team runs containerized services that need self-healing and rollouts. What fits?
Why C is the answer
Kubernetes
Kubernetes orchestrates containers.
In detail
- Kubernetes orchestrates containers, with self-healing and rollouts.
- Batch jobs often suit Slurm.
Use case
An illustrative scenario, not a real incident.
A team runs inference services that must restart themselves and roll out safely, on Kubernetes.
See it in different ways
flowchart TD
A{"What does the workload look like?"} -->|"Batch jobs"| B["Slurm"]
A -->|"Containers and services"| C["Kubernetes"]mindmap
root((Operations))
Monitoring
nvidia-smi
DCGM
Scheduling
Slurm
Kubernetes
Provisioning
Base Command Manager
Sharing
MIG
vGPUflowchart TD
Q{"What is the workload?"}
Q -->|"Containerized services"| A0["Kubernetes"]
Q -->|"Batch training"| A1["Slurm"]Key point: Kubernetes orchestrates containers.
Why the other options are wrong
- A. Docker on one host
- One host has no self-healing.
- B. Docker Compose on one host
- One host has no self-healing.
- D. Slurm
- Slurm is for batch jobs.