Hands-on Lab·Certified Kubernetes Administrator
Jobs and CronJobs
Every other controller keeps Pods running forever. A Job is the one that wants them to stop. Run four completions two at a time, read the difference between completions, parallelism and backoffLimit, then put it on a schedule and trigger it by hand.
Workloads Guide 30 of 103 Beginner
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 30 min
- Reviewed21 August 2026
Written against the versions above. Job name suffixes, timestamps and durations differ per run. The manifests are the part to copy.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- A working cluster and
kubectl. - The Deployments guide, or equivalent. A Job is a controller like any other; what differs is that success means stopping.
- Patience for one minute at the CronJob step. The shortest cron interval is a minute and there is no way to hurry it.
-
A workload that is supposed to finish
-
Completed Pods are kept, not cleaned up
-
Put it on a schedule
-
Wait for the first scheduled run
-
Trigger a run by hand
-
Clean up