A Kubernetes pod is the smallest deployable unit in Kubernetes, representing one or more tightly coupled containers that share networking, storage, and lifecycle. Also known as a K8s pod, it is the basic building block for running applications in a Kubernetes cluster.
Pods define how applications are executed in Kubernetes. Understanding pods is essential for designing scalable, resilient workloads and for using higher-level controllers like Deployments and StatefulSets effectively.
When a pod is created, Kubernetes schedules it onto a node. The kubelet on that node ensures the containers in the pod are running and healthy. If a pod fails, controllers may replace it automatically to maintain the desired state.
BuildPiper deploys and manages workloads at the pod level through Kubernetes controllers. It provides visibility into pod health and behavior, helping teams understand how deployments and releases impact running applications.
Yes. A pod can contain multiple containers that need to work closely together, such as an application container and a logging or proxy sidecar.
No. Pods are ephemeral by design. When a pod is destroyed, it is typically replaced by a new one rather than restarted.
BuildPiper correlates pod-level telemetry with deployments and environments, enabling teams to diagnose issues and assess release impact more effectively.