study.

CKAD learning path

Build multi-container applications, batch jobs, configuration injection, and controlled deployments.

Six introductory application-development labs, not a complete CKAD exam course or mock exam. Ingress, NetworkPolicy, Helm, and other advanced topics need further study.

Use kubectl, a personal practice Kubernetes cluster, and a POSIX shell. Each lab uses its own namespace. Use example values only in Secrets. Cleanup removes the entire practice namespace.

Learn with progress and quizzes

Essential concepts before you start

The application execution contract

Image, command and arguments, environment, listening ports, and required paths form the execution contract. Valid YAML can still violate it. Before deployment, describe which user runs the app, what it reads and writes, and when it is ready.

Initialization, services, and batch work

Regular init containers finish preparation before the app. Deployments maintain services; Jobs represent finishing work, and CronJobs create scheduled Jobs. Choose the workload according to whether success means completion or continued execution.

Configuration delivery and refresh

ConfigMaps and Secrets can be consumed as environment values or files. Environments are established at startup; files also require application reread behavior. Checking reference name, key, and namespace separates missing settings from image problems.

Startup, readiness, and liveness

Startup handles initialization, readiness signals serving ability, and liveness detects failures needing restart. Withholding traffic and restarting a process are different responses. Decide what action a failed probe should trigger before choosing its check.

Security and resource requirements

securityContext controls execution identity, privilege escalation, and root filesystem writes. Requests express placement needs and limits constrain execution. Understand required write paths and actual resource needs so restrictions remain compatible with correct behavior.

Rollouts and observable success

A successful apply acknowledges an API operation, not complete application success. Verify image, Ready count, and actual responses. Recovery is clearer when you know the target revision and whether configuration and data remain compatible.

Application Design

Build initialization flows and batch jobs.

Configuration & Permissions

Inject configuration and restrict process permissions.

Health & Delivery

Check readiness and choose traffic targets.