Master the 11 Core Components of Kubernetes in Minutes

Kubernetes, born from Google’s Borg system, is a powerful open‑source container orchestration platform written in Go, offering an API‑driven, high‑performance ecosystem that developers and operators can extend.

1. Pod

A Pod is the smallest deployable unit in Kubernetes, potentially containing multiple containers that share a single IP address and network namespace, often representing a single instance of a microservice.

2. Node

Nodes are the physical or virtual machines that provide compute resources for Pods, handling tasks such as data storage, job execution, workload maintenance, and network routing.

3. Label & Annotation

Labels are key‑value pairs used to group and select resources (e.g., app=worker), while Annotations store arbitrary metadata such as change reasons or version notes.

4. Service Discovery

Kubernetes uses etcd as its internal data store and provides built‑in DNS‑based service discovery, allowing Pods to resolve service names to IP addresses without additional configuration.

5. ReplicaSet

ReplicaSets maintain a desired number of Pod replicas, ensuring high availability and enabling automatic scaling based on workload demands.

6. DaemonSet

DaemonSets ensure that a single Pod instance runs on every Node, useful for cluster‑wide services like log collectors (e.g., Filebeat).

7. StatefulSet

StatefulSets manage stateful applications that require stable network identities and persistent storage, preserving pod hostnames and handling PersistentVolumeClaims.

8. Job

Jobs create Pods that run to completion for batch processing tasks, terminating once the work is finished.

9. ConfigMap & Secret

ConfigMaps provide non‑sensitive configuration data as key‑value pairs, while Secrets store encrypted sensitive information such as passwords or certificates.

10. Deployment

Deployments describe the desired state of an application and manage rolling updates, rollbacks, and scaling. Two primary update strategies are:

Replace – swaps all Pods at once, causing downtime.

Rolling Update – gradually replaces Pods using maxSurge and maxUnavailable settings to maintain service continuity.

11. Storage

Kubernetes abstracts storage via PersistentVolumes, allowing workloads to request durable storage that can outlive the lifecycle of individual Pods.

Overall, Kubernetes is designed with API‑first principles, encourages extensible tooling, and promotes declarative configuration, enabling teams to manage complex, cloud‑native workloads efficiently.