Jobs and CronJobs: Batch and Scheduled Workloads

Deployments keep Pods running. StatefulSets keep them running in order. DaemonSets keep one running per node. Jobs do the opposite: run a container, let it finish, and stop. CronJobs wrap that in a schedule.

The CKA Workloads & Scheduling domain (15%) tests your ability to create Jobs with specific parallelism and completion settings, wire up CronJobs with concurrency policies, and troubleshoot failures when a batch workload misbehaves. These same skills matter in production: database backups, etcd defragmentation, certificate rotation, and data pipeline stages all run as Jobs or CronJobs.