Kubernetes Fundamentals
How a Kubernetes cluster actually works: pods, controllers, networking, storage, and the day-to-day commands that keep it running.
kubernetesdevopsinfrastructurebeginner
41decks
41main cards
203practice cards
20%with images
v1.0.0version
Card type mix
- multiple choice: 75
- select blank: 64
- true false: 44
- multi select: 29
- match pairs: 21
- order: 7
- code fill: 3
- image choice: 1
What's covered
- The Problem Kubernetes Solves
- Kubernetes vs. Plain Docker
- Control Plane vs. Nodes
- The API Server and etcd
- etcd: The Cluster's Database
- The Scheduler
- The Kubelet and Container Runtime
- Talking to a Cluster With kubectl
- What a Pod Actually Is
- Multi-Container Pods and Sidecars
- A Pod's Lifecycle
- ReplicaSets
- Deployments
- StatefulSets
- DaemonSets
- Jobs and CronJobs
- Services: Giving Pods a Stable Address
- ClusterIP, NodePort, and LoadBalancer
- DNS Inside a Cluster
- Ingress and Ingress Controllers
- ConfigMaps
- Secrets
- Getting Config Into a Pod
- Volumes, Briefly
- PersistentVolumes and PersistentVolumeClaims
- StorageClasses and Dynamic Provisioning
- Requests and Limits
- Namespaces
- Labels and Selectors
- Node Affinity and Taints
- Liveness, Readiness, and Startup Probes
- Horizontal Pod Autoscaling
- YAML Manifests and Applying Them
- Helm Basics
- Kustomize, Briefly
- Rolling Updates and Rollbacks in Practice
- Reading Logs and Debugging a Pod
- RBAC Basics
- Resource Quotas and Limit Ranges
- Pod Disruption Budgets
- Common Kubernetes Anti-Patterns
Example cards
multiple choice
What problem does Kubernetes solve?
multiple choice
What does Kubernetes add on top of Docker?
Latest: Converted 23 practice cards that tested plain concept recall (e.g. "control plane", "a chart", "a demo") from typing types to tap-based select_blank -- typing cards should be reserved for actual kubectl/CLI syntax.