Kubernetes Simulator
intermediate · ~10 min
When a job fails
The export Job copies yesterday's orders into the data warehouse. It has been failing: a Job retries a failed pod, backing off each time, until backoffLimit is spent — then it is Failed for good.
The failed pods are still there, and so are their logs. The source database's address lives in the export-config ConfigMap. And one thing to know: a Job's pod template can't be edited once the Job exists.
Objectives
- Find out why the export fails
- Run an export Job that completes
- Bonus: Discover the template is immutable: try applying the fix before deleting the Job
Best on a computer with a keyboard. It works on a phone, with shortcuts under the terminal.