Interview Kubernetes, Docker, Helm & Podman

What is a Job versus a CronJob?

Kubernetes, Docker, Helm & Podman · Basic level

Answer

A Job runs a finite task to completion, such as a migration or batch import. A CronJob creates Jobs on a schedule, such as nightly cleanup, backup validation, or periodic reporting.

Technical explanation

Jobs track completions and retries; CronJobs add schedule, concurrency policy, and missed-run behavior.

Batch jobs need idempotency because retries can rerun the same task after partial failure.

Kubernetes workload controllers encode different lifecycle guarantees: interchangeable replicas, stable identities, node-local agents, or finite tasks.

Storage decisions must align with durability, access mode, zone placement, backup, restore, and failover behavior.

Autoscaling should be designed with metrics, scheduling constraints, PDBs, and node capacity together.

Hands-on example

1. Deploy a workload for this exercise using kubectl apply and a small test image such as nginx, busybox, or a purpose-built app: run a one-time Job and a scheduled CronJob with concurrency controls.

2. Inspect ownerReferences, events, Pods, PVCs, PVs, EndpointSlices, and metrics depending on the resource being tested.

3. Create a realistic disruption: delete a Pod, scale replicas, restart a node, fill a queue, or recreate storage attachment in a test environment.

4. Write the runbook entry covering expected behavior, safe rollback, and what alarms should exist.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions