Running Work to Completion
Run a batch workload as a Job — once, and in parallel to a fixed number of completions.
Your mission
Not every workload is a server that runs forever. A database migration, a report, a batch import — these have a beginning and an end, and success means the process exited 0, not that a Pod stayed up. A Deployment is the wrong tool: it would restart your finished task forever.
A Job runs a Pod (or several) until a set number of them complete successfully, then stops. It tracks how many have succeeded, retries failures up to a limit, and leaves its record behind so you can see the run happened.
In this lab you run a one-shot Job, then a fixed batch that completes several times in parallel.
Useful aliases
In your terminal, k is aliased to kubectl and completion is configured. The
jumpbox also has k9s, jq and yq installed.