Understanding Kubernetes Architecture and Its Role in Cloud‑Native Environments

Kubernetes (K8s) is an open‑source platform for managing containerized applications across multiple hosts, aiming to simplify and automate deployment, scaling, and maintenance.

Key Characteristics of K8s

Portability – supports public, private, hybrid, and multi‑cloud environments.

Scalability – modular, pluggable, and composable architecture.

Automation – automatic deployment, restart, replication, and scaling.

Enterprise Use Cases

Small‑to‑medium businesses use K8s to build automated operation platforms that handle application deployment, planning, updates, and maintenance, while large internet companies rely on it for large‑scale containerized deployments and automated monitoring.

Resource Utilization Example

Assuming 200 concurrent requests (150 static, 50 dynamic) on a server with 2 CPU and 4 GB RAM, static requests consume 2 MB each and dynamic requests 10 MB each, resulting in 800 MB memory usage and a theoretical QPS of 800 (conservatively limited to ~300 QPS in practice).

Service Migration and Deployment Evolution

Traditional physical servers bind applications to the host OS, causing environment inconsistencies. Containerization packages each service into an image that runs independently of the underlying infrastructure, enabling seamless migration from development to production.

Deployment models have evolved from physical machines to virtual machines (which are resource‑heavy) and finally to containers, which are lightweight, isolated, and portable across clouds.

Challenges in Container Deployment

Horizontal scaling of services.

Handling container failures and recovery.

Zero‑downtime version updates.

Monitoring containers.

Scheduling and creation of containers.

Ensuring data security.

Kubernetes addresses all these challenges.

Cloud‑Native Concepts

Cloud‑native solutions run all services in containers, adopt micro‑service architectures, use CI/CD pipelines, and integrate DevOps practices.

Kubernetes Architecture Overview

A Kubernetes cluster consists of a single master node and multiple worker nodes.

Master Node Components

API Server – the gateway for all commands.

Scheduler – assigns workloads to nodes based on scheduling algorithms.

Controller – manages CRUD operations for Kubernetes resources.

etcd – stores resource definitions and supports service discovery.

Worker Node Components

Docker – container runtime.

Kubelet – runs on each node, watches etcd for instructions and manages pods.

Kube‑proxy – provides load balancing across pods.

Fluentd – collects logs.

Pod – the smallest deployable unit, which may contain one or more containers.

Architecture Recap

K8s manages containers indirectly via pods.

One master controls many nodes.

Master handles scheduling, API gateway, controllers, and resource storage; it does not run containers.

Containers run inside pods on worker nodes.

Kubelet maintains pod lifecycle; kube‑proxy balances traffic among pods.