What Is Kubernetes? Core Concepts, Architecture, and Key Components Explained

Introduction

Kubernetes (k8s) is an open‑source container orchestration platform that manages containerized applications across multiple hosts. It provides rapid deployment, scaling, and rolling updates, service registration and discovery via Service, and layer‑7 load balancing through Ingress. The project was open‑sourced by Google in 2014 and is now maintained by a large community.

Advantages of Container Orchestration

Flexible deployment : Supports private, public, hybrid, and multi‑cloud environments.

Security and efficiency : Implements role‑based access control (RBAC) and other security mechanisms.

Load balancing : Provides layer‑4 ( Service) and layer‑7 ( Ingress) load balancing.

Key Features

Multi‑tenant network isolation via Namespace High availability and horizontal scalability

Resource efficiency and hardware optimization

Typical Use Cases

DevOps integration (development‑operations convergence)

Micro‑service architectures

Characteristics

Portability : Runs on public, private, hybrid, and multi‑cloud environments.

Extensibility : Modular, plug‑in‑friendly, mountable, and composable.

Self‑healing : Automatic pod placement, restart, replication, and scaling.

Core Capabilities

Process coordination with a one‑to‑one container‑application model

Mounting of external storage systems

Distribution of secrets

Application health checks

Pod replication

Horizontal pod autoscaling (HPA)

Service discovery and DNS naming

Load balancing (IPVS or iptables)

Rolling updates

Resource monitoring

Log access

Self‑diagnosis and debugging

Identity and authentication

Architecture

Kubernetes follows a master‑node (control‑plane/worker) model. A typical highly available control plane consists of three to five master nodes; the number of worker nodes scales with the size of the cluster.

Core Control‑Plane Components

kube‑apiserver : Central entry point for all API requests; handles authentication, authorization, admission control, API registration, and discovery.

kube‑scheduler : Assigns pods to nodes based on resource availability, taints/tolerations, affinity rules, and other scheduling policies.

kube‑controller‑manager : Runs built‑in controllers (e.g., replication, endpoint, service, node) that maintain the desired state of the cluster.

etcd : Distributed key‑value store that persists the entire cluster state. Network plugins such as Calico store their configuration in etcd, while Kubernetes stores object metadata and status.

Note: network plugins typically use the v2 API, whereas Kubernetes components use the v3 API; set the ETCDCTL_API environment variable accordingly when using etcdctl.

kube‑proxy : Runs on every node; translates Service definitions into IPVS or iptables rules to provide load‑balancing for backend pods.

CoreDNS : DNS server that supplies DNS records for services (replaced kube‑dns from Kubernetes v1.11 onward).

Calico : Layer‑3 network plugin that provides networking and network‑policy enforcement.

kubelet : Node‑level agent that registers the node with the API server, monitors pod specs, and starts/stops containers via the container runtime.

Container runtime : Docker is the default runtime in many installations, but alternatives such as containerd or CRI‑O are also supported.

Node‑Side Components

kubelet : Manages pod lifecycle on worker nodes, reports status to the API server.

kube‑proxy : Handles network forwarding and load‑balancing on each node.

Calico : Enforces network policies and provides L3 connectivity on worker nodes.

Docker (or alternative runtime) : Executes container workloads.

Additional Add‑On Components

Dashboard : Web UI for visual management of Kubernetes resources.

Ingress Controller : Implements layer‑7 load balancing (e.g., Nginx, Traefik) for HTTP/HTTPS routing.

Monitoring stack : Prometheus, Alertmanager, and Grafana provide metrics collection, alerting, and visualization.

Logging stack : Elasticsearch‑Fluentd‑Kibana (EFK) pipeline for centralized log aggregation and analysis.

Metrics Server : Supplies resource usage metrics required by the Horizontal Pod Autoscaler.

References

GitHub repository: https://github.com/kubernetes/kubernetes Official documentation: https://kubernetes.io/ and

https://kubernetes.io/docs/