Certified Kubernetes Application Developer (CKAD)

When application teams ship to Kubernetes without shared standards, risk follows: misconfigured secrets, unchecked resource use, untested rollouts, and endpoints exposed without TLS. This CKAD course gives IT Directors a single path to align developers and DevOps engineers on how production-scale applications are built, configured, secured, and exposed on Kubernetes.

Role fit: This course suits application developers working alongside a DevOps team, and DevOps engineers with about six months of relevant experience. Platform owners responsible for cluster administration may be better served by the companion CKA course.

Time investment: Plan for about 47 hours across 46 skills per learner, plus hands-on practice time. The CKAD is a scenario-driven exam taken in a live shell, so conceptual study alone will not prepare your team. The trainer stresses practicing every exercise with kubectl on a working cluster. Learners build their own clusters, either locally with K3s and Multipass or in an approved cloud sandbox environment.

Risk and governance: Coverage includes Secrets, ServiceAccounts, network policy, TLS with cert-manager, and namespace quotas. These are the controls that support security reviews and fair compute sharing.

Change management: Later skills introduce GitOps with ArgoCD and GitHub SSH authentication. Team Leads should expect workflow changes and coordinate adoption across repositories.

IT teams complete this training to move Kubernetes work from trial-and-error to repeatable, production-ready practice. The CKAD exam is scenario-driven: candidates run commands in a live shell. Because of that, the course teaches through hands-on cluster work rather than theory alone. Instructor Trevor Sullivan emphasizes practical Kubernetes work, so practitioners build the kubectl command familiarity they need on the job.

How this training helps your team succeed:

• Faster, safer releases. Your team builds GitOps pipelines with ArgoCD and deploys from GitHub Actions. Every change is traceable in Git, and container images flow from build to registry to cluster without manual steps.
• Shorter troubleshooting cycles. Practitioners check container logs, exec into running pods, and turn on debug logging for components such as ExternalDNS. This helps them find the root cause of an issue instead of escalating it.
• More resilient applications. Your team practices Kubernetes application design and deployment patterns for containerized workloads, including building images, deploying them to clusters, and configuring workloads so applications keep running reliably as the environment changes.
• Stronger security around exposed services. Engineers manage Secrets and ConfigMaps, apply network policy, and secure external endpoints with TLS through cert-manager. They also learn to protect sensitive admin interfaces with authentication and cloud firewall controls.

The result is a development team that can design, configure, and expose cloud-native applications that a DevOps organization can run at production scale.

Knowledge

• How core Kubernetes primitives fit together: Pods as the foundation for higher-level constructs like ReplicaSets, Deployments, Jobs, CronJobs, and StatefulSets
• How ConfigMaps, Secrets, and ServiceAccounts separate configuration and credentials from application code
• How scheduling controls work, including taints, PriorityClass preemption, resource limits, and namespace quotas
• How Services, Ingress, and NetworkPolicy expose and protect applications
• How persistent storage works for stateful workloads, including persistent volumes, persistent volume claims, storage classes, and shared volumes used by multi-container Pods
• How CI/CD practices help standardize container image builds and Kubernetes manifest deployments for repeatable application releases

Ability

• Deploy and connect kubectl to Kubernetes clusters in managed cloud or local lab environments
• Configure startup, liveness, and readiness probes, and use init containers and sidecar patterns, such as a log-reader container on a shared volume
• Run Jobs with completions, parallelism, and failure handling, and schedule recurring work with CronJobs
• Perform rolling updates, then troubleshoot workloads with container logs, debug-level logging, and interactive shells inside Pods
• Validate Kubernetes manifests as part of a CI/CD workflow, build container images, push images to a registry, and deploy workloads to a cluster
• Complete hands-on, command-line tasks in a shell environment that reflect the scenario-driven skills measured by the CKAD exam