study.

Kubernetes learning path

Move from reading resources to deploying, connecting, configuring, and recovering applications.

Six labs cover core concepts and operational workflow. Cluster installation, production high availability, and installing a GitOps controller are outside this course.

Use kubectl, a personal practice Kubernetes cluster, and a POSIX shell. Check the context and use the dedicated namespace in each lab. Cleanup deletes all resources in that practice namespace.

Learn with progress and quizzes

Essential concepts before you start

Clusters and Nodes

A cluster manages desired state through APIs and controllers and runs workloads on Nodes. A Node is a machine that executes Pods. Storing a request in the cluster and having a ready application on a node are separate milestones.

Declarative APIs and reconciliation

spec describes intent and status reports observations. Controllers repeatedly reduce the difference. Declaring three replicas can cause a replacement when one disappears, but insufficient resources can prevent immediate convergence.

Pods and Deployments

A Pod groups co-located containers with shared networking and volumes. A Deployment manages a Pod template, replicas, and updates. For continuously running services, understand controller ownership and replacement rather than treating a standalone Pod as permanent.

Namespaces, labels, and selectors

Namespaces scope names, labels classify objects, and selectors identify matching sets. A Service can select app=web Pods in team-a. Adding a label does not automatically configure access permissions or network isolation.

Services and cluster DNS

A Service supplies a named entry point in front of changing Pods. DNS resolves the name; backend selection and packet forwarding are distinct responsibilities. Successful lookup can still be followed by HTTP failure due to ports or readiness.

Configuration and persistent data

ConfigMaps supply ordinary settings, Secrets carry sensitive settings, and PVCs request persistent storage. Separating image, environment configuration, and user data helps reuse images and decide what must survive replacement.

API & Desired State

Read resource structure and observe controller behavior.

Services & Configuration

Connect by name and separate configuration from code.

Changes & Recovery

Deploy overlays and recover from a bad change.