CKAD: Application Developer Foundations

Schedule a recurring Job with a CronJob, then suspend it the way you'd pause a scheduled backup — without deleting it.

Run a helper alongside your app in the same Pod — the sidecar pattern — sharing the Pod's network and lifecycle.

Run setup logic to completion before your app starts, in an init container — and see why it isn't just another sidecar.

Give a container its own identity — pod name, namespace, node and IP — through the Downward API instead of hardcoding it.

Drop a workload's privileges: run as non-root, forbid privilege escalation, make the root filesystem read-only, and drop all Linux capabilities.

Give a workload storage that survives a restart: claim a PersistentVolume and mount it, and understand why the claim only binds once a Pod needs it.

Tune a Deployment's rollout strategy for zero downtime, then ship a new image version without dropping a request.

Expose an internal Service to the outside world over HTTP with an Ingress rule — host, path and backend.

Lock a namespace down with a default-deny, then open one precise path with a from-and-port allow rule.

Exam-pace drill: in one sitting, wire up config, a resourced and probed Deployment, durable storage, a Service and an Ingress — each task fuses several skills, like the real thing.

Exam-pace drill: give a workload a scoped identity (ServiceAccount + RBAC), lock the container down, and isolate it with a NetworkPolicy — exact specs, costly hints, tight timer.

Exam-pace drill: stand up a probed, rolling Deployment; ship a new version zero-downtime while scaling; then front it with a Service and protect it with a PodDisruptionBudget.