What is Pod?
A Pod is the smallest deployable unit in Kubernetes, representing one or more containers that share network, storage, and lifecycle.
A Pod is the basic execution unit of a Kubernetes application. It encapsulates one or more containers, storage resources, a unique network IP address, and options that govern how the containers run. Containers within a Pod share the same network namespace, meaning they can communicate over localhost, and they share the same storage volumes. Pods are designed to support co-scheduled, co-located processes that form a single unit of service, such as a web server container with a helper container that syncs files.
Pods are created and managed by higher-level controllers like Deployments, StatefulSets, or DaemonSets. A Pod's lifecycle is tied to its phase: Pending, Running, Succeeded, Failed, or Unknown. If a Pod fails, the controller will replace it according to the desired replica count. Pods are ephemeral; they restart only through controllers. Direct pod creation is uncommon in production because controllers handle resilience.
Pods sit at the core of Kubernetes scheduling. The kubelet on each node creates and monitors Pods. Networking is handled by the cluster's CNI plugin, which assigns each Pod an IP from the cluster's CIDR range. Storage is attached via PersistentVolumeClaims or ephemeral volumes. Pods are the atomic unit for scaling, resource requests, and horizontal pod autoscaling.
Key facts
- A Pod can contain one or more containers that share the same network namespace and IP address.
- Containers in a Pod can communicate via localhost and share mounted volumes.
- A Pod represents a single instance of a running process in a Kubernetes cluster.
- Pods are usually managed by controllers like Deployments, not created directly.
- Each Pod gets a unique IP address within the cluster network, assigned by the CNI plugin.
How it works in practice
Related terms
References
More in Containers & Orchestration
ConfigMap
A ConfigMap is a Kubernetes API object used to store non-confidential configuration data in key-value pairs, which pods can consume as environment variables, command-line arguments, or configuration files.
Container
A container is a lightweight, isolated runtime that packages an application with its dependencies using OS-level virtualization, enabling consistent execution across environments.
Container Image
A container image is a lightweight, standalone, executable package that includes everything needed to run a piece of software: code, runtime, system tools, libraries, and settings. It is the unit of distribution in container ecosystems like Docker and Kubernetes.
Container Registry
A container registry is a service that stores and distributes container images, enabling developers to push, pull, and version images across environments.
Container Runtime
A container runtime is the low-level software that creates, starts, and stops containers according to the OCI runtime specification, enabling process isolation and resource management.
Docker
Docker is a platform and toolchain for packaging, distributing, and running applications inside lightweight, portable containers, popularising the technology from 2013 onward.
Helm
Helm is a package manager for Kubernetes that uses charts to define, install, and upgrade complex applications as a single, versioned unit.
Ingress Controller
An Ingress Controller is a Kubernetes component that watches Ingress resources and configures a reverse proxy to route external HTTP and HTTPS traffic to services inside the cluster.
Init Container
An init container is a specialized container in a Kubernetes pod that runs to completion before any regular containers start, performing initialization or setup tasks.
Kubernetes
Kubernetes is an open source platform for automating the deployment, scaling, and management of containerized applications across clusters of hosts.