Jobs and CronJobs

Not every workload runs forever. Database migrations, nightly backups, report generation, batch ETL pipelines: these need to run, finish, and get out of the way. Deployments and DaemonSets are wrong for this. They restart containers indefinitely, which is exactly what you don't want when the work is done.

Jobs and CronJobs are the Kubernetes batch primitives. A Job runs one or more Pods to completion and tracks how many succeeded. A CronJob wraps a Job template in a cron schedule. Both live in the batch/v1 API group, and the CKAD exam (Application Design and Build, 20%) expects you to create them quickly from the command line, configure parallelism, set schedules, and debug failures.