What Is Kubernetes and Why Is It Hard to Get Started?

Kubernetes is a container‑based distributed cluster management system that stems from Google’s extensive experience with large‑scale container deployment.

The platform consists of multiple Nodes (physical or virtual machines) managed by a Master node, forming a distributed cluster.

Question 1: How do the Master and Worker nodes communicate? When the Master starts, the kube-apiserver process provides the API interface for all components. Each Node runs a kubelet process that reports its status to the Master and receives commands to create Pods. A Pod is the basic execution unit and may contain one or more containers that share a network namespace via a special pause container.

Question 2: How does the Master schedule Pods onto specific Nodes? The kube-scheduler runs complex algorithms (e.g., round‑robin) to select the optimal Node for each Pod. Users can influence placement by labeling Nodes and using a Pod’s node selector to match those labels.

Question 3: Where is information about Nodes and Pods stored? All cluster configuration and state are kept in etcd , a highly available key‑value store. The kube-apiserver acts as the gateway for internal components and external users to read or modify this data via RESTful APIs.

Question 4: How do external users access Pods? Kubernetes introduces the Service abstraction, which groups Pods with the same labels and provides a stable virtual IP. A kube-proxy on each Node routes traffic from the Service IP to the appropriate Pod(s), handling load balancing across multiple instances.

Question 5: How are Pods dynamically scaled? The Replication Controller (or ReplicaSet) maintains a desired replica count for each Pod. If the actual number deviates, the controller creates or deletes Pods to match the target, enabling manual or automatic scaling.

Question 6: How do the various components cooperate? The kube-controller-manager runs multiple controllers (Service, Replication, Node, ResourceQuota, Namespace, etc.) that watch the cluster state via the apiserver and act to reconcile the actual state with the desired state. Each controller forms a control loop that continuously ensures consistency.

Summary This article provides a conceptual overview of Kubernetes core concepts—including Nodes, Pods, Labels, Selectors, various Controllers, and the main processes such as kube-apiserver , kube-controller-manager , kube-scheduler , kubelet , kube-proxy , and the pause container.