Cloud Native 10 min read

Unlocking Kubernetes Architecture: From Pods to High‑Availability Design

This article provides a comprehensive overview of Kubernetes architecture, covering its core components, service discovery methods, pod shared resources, common CNI plugins, multi‑layer load balancing, isolation dimensions, and network model principles that enable scalable, high‑availability container operations.

Java High-Performance Architecture
Java High-Performance Architecture
Java High-Performance Architecture
Unlocking Kubernetes Architecture: From Pods to High‑Availability Design

Overview

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

Key Functions

Automated container deployment and replication.

Real‑time elastic scaling of container workloads.

Container orchestration with built‑in load balancing.

Core Components

kubectl – command‑line client.

kube‑apiserver – REST API entry point.

kube‑controller‑manager – runs background control loops.

kube‑scheduler – assigns Pods to nodes.

etcd – highly available key‑value store for configuration and service discovery.

kube‑proxy – network proxy on each node.

kubelet – node‑level agent that manages Pods.

DNS – optional service for creating DNS records for Services.

Architecture Highlights

Typical deployment includes a local production center, a local disaster‑recovery center, and an off‑site disaster‑recovery center, with etcd providing strong consistency.

Service Discovery

K8s supports two native mechanisms: environment‑variable injection (limited) and DNS via the kube‑dns add‑on.

Pod Shared Resources

Containers in the same Pod share PID, network, IPC, UTS namespaces and Volumes, enabling localhost communication.

CNI Plugins

Common CNI (Container Network Interface) plugins provide standardized networking and resource cleanup for containers.

Load Balancing Layers

Layer 2 – MAC‑based load balancing.

Layer 3 – IP‑based load balancing.

Layer 4 – IP + port load balancing.

Layer 7 – URL/application‑level load balancing (Ingress).

Isolation Dimensions

Network Model Principles

Each Pod receives a unique IP address (IP‑per‑Pod model), allowing flat, directly reachable networking across the cluster without NAT.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Cloud NativeKubernetesload balancingservice discoveryCNIcontainer orchestrationPod Architecture
Java High-Performance Architecture
Written by

Java High-Performance Architecture

Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.