CKA-33-Kubernetes Jobs

Learn how Kubernetes Jobs run reliable, finite batch workloads and how to configure completions and retries.

For CKA preparation, do not treat this as a definition to memorize. Treat it as a cluster behavior you should be able to inspect, configure, and verify under time pressure. This guide explains the operational purpose, the important moving parts, and a safe way to reason about it.

What you will learn: how jobs fits into workloads and scheduling, what to check first, and the mistakes that commonly lead to failed changes.

Running finite tasks until they finish successfully

Deployments keep applications running. Jobs run work that is expected to complete: a database migration, report generation, batch import, or one-time cleanup.

apiVersion: batch/v1
kind: Job
metadata:
  name: generate-report
spec:
  backoffLimit: 3
  template:
    spec:
      restartPolicy: Never
      containers:
        - name: report
          image: example/report-generator:1.0
          args: ["--date", "2026-06-20"]

The Job creates a Pod and tracks its completion. If the container fails, retry behavior depends on restartPolicy, backoffLimit, and other settings. Once the required completions succeed, the Job is complete.