Skip to content
How Does Kubernetes Actually Create a Pod? Step‑by‑Step Walkthrough
Cloud Native 3 min read

How Does Kubernetes Actually Create a Pod? Step‑by‑Step Walkthrough

This article walks through every stage of how Kubernetes creates a pod—from submitting the YAML to the API, through etcd storage, scheduling, kubelet and CRI actions, CNI networking, and endpoint setup for services—providing a clear, step‑by‑step visual guide.

MaGe Linux Operations
MaGe Linux Operations
MaGe Linux Operations

Deploying a Pod in Kubernetes involves several distinct phases.

kubectl sends the YAML manifest to the API server.

The Pod definition is stored in etcd.

The scheduler assigns the Pod to a node (the Pod manifest remains in etcd; the node does not yet have the Pod).

kubelet begins creating the Pod.

kubelet delegates container creation to the Container Runtime Interface (CRI).

kubelet connects the container to the CNI network.

CNI allocates an IP address for the Pod.

Readiness/liveness probes run; kubelet reports the Pod IP back to the control plane.

At this point the Pod is fully created. If the Pod is part of a Service, Kubernetes also creates an endpoint object that links the Pod’s IP address and targetPort.

These endpoints are used by: kube-proxy to set iptables rules. CoreDNS to update DNS entries. Ingress controllers to configure downstream services ( downstreams).

Service meshes.

Other operators.

Deleting a Pod follows the same steps in reverse order.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

KubernetesServiceCRICNIPodEndpoint
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.