29/05/2026
๐ Kubernetes Architecture Explained Simply โธ๏ธ
Most people use Kubernetes dailyโฆ
But very few truly understand what happens behind the scenes. ๐
Hereโs a simplified view of the Kubernetes Architecture ๐
๐ง Control Plane (Master Node)
This is the brain of Kubernetes.
It manages the entire cluster and makes decisions like:
โ
Scheduling containers
โ
Maintaining desired state
โ
Scaling workloads
โ
Managing networking
Key Components:
๐น kube-apiserver
The main entry point of the cluster.
Every command (kubectl, CI/CD pipeline, Terraform, etc.) talks to the API Server first.
๐น etcd
The database of Kubernetes.
Stores cluster state, configurations, secrets, and metadata.
๐น kube-scheduler
Decides where Pods should run based on resources and policies.
๐น controller-manager
Ensures the cluster always matches the desired state.
๐น cloud-controller-manager
Connects Kubernetes with cloud providers like Azure, AWS, or GCP.
๐ป Worker Nodes
These are the machines where applications actually run.
Each node contains:
๐น kubelet
Communicates with the Master Node and ensures containers are running properly.
๐น kube-proxy
Handles networking and service communication between Pods.
๐ฅ Simple Workflow
1๏ธโฃ Developer deploys application using YAML / Helm / Terraform
2๏ธโฃ Request reaches kube-apiserver
3๏ธโฃ Scheduler selects best node
4๏ธโฃ kubelet starts containers
5๏ธโฃ kube-proxy manages networking
6๏ธโฃ etcd stores cluster state
๐ก Why This Matters for DevOps Engineers
Understanding Kubernetes architecture helps in:
โ
Troubleshooting cluster issues
โ
AKS/EKS/GKE administration
โ
Performance optimization
โ
CI/CD integration
โ
Scaling microservices
โ
Cloud-native deployments
๐ฏ Interview Killer Line
โKubernetes works on a declarative desired-state model where the control plane continuously ensures that the actual cluster state matches the expected state.โ
๐ Which Kubernetes component do you troubleshoot the most?
kubelet
API Server
etcd
Networking issues ๐
