Mastering Kubernetes: From Container Basics to Massive Scale

Goal Overview

Container operations, two‑site three‑center architecture, four‑layer service discovery, five shared Pod resources, six common CNI plugins, seven‑layer load balancing, eight isolation dimensions, nine network model principles, ten IP address categories, and massive scaling capabilities.

What Is Kubernetes?

Kubernetes (k8s) is an open‑source platform for automated container operations, including deployment, scheduling, and elastic scaling across node clusters.

Key Functions

Automated container deployment and replication.

Real‑time elastic scaling of container workloads.

Container grouping with built‑in load balancing.

Scheduling containers onto specific nodes.

Core Components

kubectl – command‑line client.

kube‑apiserver – REST API entry point.

kube‑controller‑manager – background tasks such as node status, pod counts, and service associations.

kube‑scheduler – assigns pods to nodes based on resource availability.

etcd – highly available, strongly consistent key‑value store for configuration sharing and service discovery.

kube‑proxy – runs on each node to handle pod network proxying.

kubelet – node‑level agent that manages pod lifecycle and reports status.

DNS – optional service that creates DNS records for each Service.

Two‑Site Three‑Center Architecture

Consists of a local production center, a local disaster‑recovery center, and a remote disaster‑recovery center. etcd provides high‑availability, strong consistency for configuration sharing and service discovery.

Four‑Layer Service Discovery

Kubernetes supports two native service‑discovery methods:

Environment variables injected by kubelet (limited by creation order).

DNS via the kube‑dns add‑on.

Both operate on top of the TCP/IP stack, while DNS uses UDP.

Five Shared Pod Resources

PID namespace – processes can see each other.

Network namespace – shared IP and port range.

IPC namespace – SystemV IPC or POSIX message queues.

UTS namespace – shared hostname.

Volumes – shared storage defined at the pod level.

Six Common CNI Plugins

CNI (Container Network Interface) provides a standard framework for container networking. The six widely used plugins are illustrated below.

Seven‑Layer Load Balancing

Load balancing at different OSI layers:

Layer 2 – MAC‑based.

Layer 3 – IP‑based.

Layer 4 – IP + port.

Layer 7 – URL and application‑level information.

Eight Isolation Dimensions

Kubernetes scheduling must respect isolation from coarse‑grained to fine‑grained dimensions.

Network Model Principles

K8s networking follows four basic principles, three network‑requirement principles, one architecture principle, and one IP principle. Each pod receives a unique IP address, enabling flat, directly reachable networking across the cluster.

IP Address Classification

Class A – 1.0.0.0 to 126.255.255.255 (/8).

Class B – 128.0.0.0 to 191.255.255.255 (/16).

Class C – 192.0.0.0 to 223.255.255.255 (/24).

Class D – 224.0.0.0 to 239.255.255.255 (multicast).

Class E – 240.0.0.0 to 255.255.255.255 (research).

Special addresses: 0.0.0.0 (default route), 127.0.0.1 (loopback), 169.254.x.x (APIPA), private ranges 10.x.x.x, 172.16‑31.x.x, 192.168.x.x.