Before the cluster
From a process on a machine to a container in a distributed system.
Open local exercise →A connected path from foundations to production operations and internals. Follow the sequence, or go directly to the question you are working on.
0 of 60 lessons completed. Saved in this browser.
Start with the primitives. Build an application, trace its traffic, and learn how the cluster keeps its promises.
From a process on a machine to a container in a distributed system.
Open local exercise →Follow an intention through the control plane and onto a worker.
Open local exercise →Describe, find, organize, and safely address Kubernetes objects.
Open local exercise →Understand the smallest scheduling unit and its configuration.
Open local exercise →Move from individual Pods to managed application releases.
Open local exercise →Give disposable Pods stable discovery and trace a broken request.
Open local exercise →Turn a running application into a reliable system. Work through scheduling, networking, data, trust, diagnosis, and delivery.
Explain why a Pod runs here, waits there, or competes for resources.
Open local exercise →Separate connectivity, routing, policy, and implementation.
Open local exercise →Connect a workload to storage with explicit lifecycle rules.
Open local exercise →Match identity, locality, and completion to a controller.
Open local exercise →Distinguish who you are, what you can do, and what may run.
Open local exercise →Build an evidence-driven path from symptom to responsible layer.
Open local exercise →Make releases reproducible and scale the actual bottleneck.
Open local exercise →Study the machinery beneath the API, then use it to design resilient control planes and extensible platforms.
Follow requests, watches, ownership, and admission at the API boundary.
Open local exercise →Discover the machinery that makes eventual convergence practical.
Open local exercise →Turn a domain-specific intention into a safe Kubernetes API.
Open local exercise →Connect measured demand to resources, queues, and failure behavior.
Open local exercise →Protect the coordination system and practice recovery deliberately.
Open local exercise →Apply Kubernetes as a platform with explicit trust and delivery boundaries.
Open local exercise →Run three cumulative investigations across the whole stack.
Open local exercise →