Skip to main content
DevOps

Kubernetes Tutorial with Examples.

Kubernetes tutorial with examples: container orchestration with pods, deployments, services, ConfigMaps, Secrets, autoscaling and Helm charts.

Architecture at a glance

Click any box to open the lesson that teaches it

Kubernetes architecture at a glance

kubectl apply → control plane → nodes → Pods, and how traffic finds them

Kubernetes architecture at a glance kubectl sends manifests to the API server in the control plane, which stores state in etcd and works with the scheduler and controller manager. Deployments own ReplicaSets, and the HPA scales them. Two worker nodes each run a kubelet, kube-proxy and a container runtime that start Pods. Users reach Pods through an Ingress and a Service. Tooling and guardrail lessons sit at the bottom right. You YAML kubectl apply · get Control plane API server authn · RBACadmission etcd stored cluster state Scheduler picks a node Controller manager reconcile loops Deployment rollout · rollback ReplicaSet keeps N Pods HPA scales on CPU Pod specs to the kubelets Worker node 1 Worker node 2 kubelet kube-proxy Container runtime Pods requests · probes Config & storage ConfigMaps · Secrets kubelet kube-proxy Container runtime Pods replicas spread DaemonSet Pod one per node Users HTTP Ingress host · path Service stable IP · DNS matching Pods Tooling and guardrails Helm RBAC · NetPol Pod Security kube-bench GitOps Strategies
How it fits together (6 steps)
  1. You declare the desired state in YAML and send it with kubectl; apply returns once the API server has stored it.
  2. The API server is the only door to etcd. Every request passes authentication, RBAC and admission first.
  3. The scheduler picks a node for each Pod, using its resource requests. Controllers run reconcile loops: a Deployment owns a ReplicaSet, which keeps N Pods alive, and the HPA changes N from real CPU numbers.
  4. On each node, the kubelet asks the container runtime to start the Pod's containers and runs its probes. Config and storage come from ConfigMaps, Secrets and volumes.
  5. Traffic: Ingress routes HTTP to a Service, a stable name and IP that kube-proxy load-balances across the matching Pods.
  6. Around the cluster: Helm packages and rolls back releases. Lessons from other topics add Pod Security admission, a CIS benchmark, GitOps and deployment strategies.

Beginner

Start here — no prior experience needed

3 lessons

Intermediate

For developers with core concepts down

6 lessons

Advanced

Production-grade patterns for experienced engineers

1 lesson

Also part of Kubernetes

Taught in other topics. Each link opens the lesson in its home topic.

5 lessons