Run Jobs and CronJobs

CKAD v1.35 · Application Design and Build (20%) → "Choose and use the right workload resource (Deployment, DaemonSet, CronJob, etc.)" Target time: 15 minutes

The browser lab provides Kubernetes 1.35, kubectl, jq, and image registry access.

Namespace batch-work is empty. Build finite and scheduled workloads using busybox:1.36 with restartPolicy: Never.

1. Job report: three successful completions, parallelism 2, backoffLimit 1, activeDeadlineSeconds 120. Each execution prints exactly report-ok and exits successfully. Wait for the Job to complete.
2. CronJob nightly: daily at 02:15 UTC using the explicit timeZone field. Use concurrencyPolicy: Forbid, startingDeadlineSeconds 120, successful history 2, failed history 1. Suspend it while validating the template.
3. Its Job template has backoffLimit 1, activeDeadlineSeconds 120, and prints exactly nightly-ok before exiting successfully.
4. Create Job nightly-manual FROM the CronJob and wait for completion. The grader compares its pod specification with the CronJob template and checks actual execution logs.
5. Leave the CronJob suspended to avoid future scheduled work after the drill. Explain how to activate it and why Forbid does not constrain manually created Jobs or other CronJobs.

Reset deletes the whole batch-work namespace. Do not place unrelated work there. The drill verifies configuration and manual execution, not the passage of a day or an actual overlap between scheduled runs. No TTL should delete evidence before grading.