A handful of containers running on one machine is easy to manage by hand — dozens or hundreds spread across a fleet of servers is not. This module covers Kubernetes: the building blocks of pods, deployments, and services, and how the control plane keeps your desired state running automatically, restarting failed containers and rescheduling work when a node goes down.
It also covers scaling, managing configuration and secrets, exposing applications to the outside world with ingress, and a first look at service meshes — the extra layer teams add once a cluster's internal traffic gets complex enough to need its own observability and control.
Watch the lessons in order, then continue on to Infrastructure as Code.
What breaks down once you're running containers at scale, and how an orchestrator like Kubernetes takes over scheduling, healing, and networking.
The core objects and components — pods, nodes, the API server, scheduler, and etcd — and how they fit together in a cluster.
Declaring the desired state for your application and letting Kubernetes handle rolling updates, rollbacks, and keeping the right number of pods alive.
How Services give a stable address to a set of ever-changing pods, and the differences between ClusterIP, NodePort, and LoadBalancer types.
Separating configuration and sensitive data from your application code, and scaling workloads manually or automatically with the Horizontal Pod Autoscaler.
Routing external HTTP(S) traffic into the cluster with Ingress resources and controllers, including basic path and host-based rules.
Using Helm charts to template, version, and reuse Kubernetes manifests instead of hand-writing YAML for every environment.
What a service mesh like Istio or Linkerd adds on top of Kubernetes networking — traffic control, mutual TLS, and observability between services.
A written reference covering core Kubernetes objects, kubectl commands, and YAML manifest structure from this module — good for a quick lookup after watching the videos.
Article