Skip to main content
Welcome. In this lesson we cover the core Kubernetes concepts you need to understand how applications run on a cluster. We’ll follow a clear sequence so you can build from high-level architecture down to the API objects you use every day.
  • First — cluster architecture: nodes, control plane components, and how they interact.
  • Next — API primitives: Pods, ReplicaSets, and Deployments (what they represent and when to use each).
  • Finally — Services and network primitives: exposing workloads, service types, and basic networking patterns.
If you’ve already completed the Kubernetes for the Absolute Beginners (hands-on) or the Certified Kubernetes Application Developer (CKAD) course, you can selectively skip sections and focus on the practice tests and hands-on labs.
A presentation slide titled "Core Concept" lists three numbered items: 01 Cluster Architecture, 02 API Primitives, and 03 Services and Other Network Primitives. A presenter stands on the right side speaking to the camera.
Suggested approach: follow the sequence — architecture → API primitives → networking — so you understand why objects exist before learning how to use them. Keep kubectl access to a test cluster ready for the hands-on exercises.
Learning objectives
  • Describe the high-level components of a Kubernetes cluster (control plane, nodes, etcd, kubelet, kube-proxy).
  • Explain Pods, ReplicaSets, and Deployments and the lifecycle differences among them.
  • Configure Services to expose workloads and understand service types (ClusterIP, NodePort, LoadBalancer).
  • Apply basic kubectl commands to inspect resources and troubleshoot common issues.
What this lesson covers (outline)
  1. Cluster architecture — control plane and worker node responsibilities.
  2. API primitives — Pod anatomy, ReplicaSet scaling, Deployment rollouts and rollbacks.
  3. Services & networking — service discovery, basic network policies, and common exposure patterns.
Quick reference table Recommended prerequisites
  • Basic familiarity with containers and Docker.
  • kubectl configured to target a Kubernetes cluster (minikube, kind, or a cloud cluster).
  • Command-line access to perform kubectl operations.
Further reading and references
Hands-on tip: never run commands against a production cluster unless you understand the object being changed. Use namespaces and test clusters for practice.

Watch Video