How Kubernetes Coordinates Through API State
Follow one Deployment from accepted intent through reconciliation, placement, node execution and readiness, then diagnose where the system can stall.
See what happens across pods, nodes, clusters, controllers, and the network between them.
6 visualizations
Follow one Deployment from accepted intent through reconciliation, placement, node execution and readiness, then diagnose where the system can stall.
Follow a Pod's DNS lookup through resolver search rules, CoreDNS, Kubernetes records, caches, and upstream resolvers.
Follow an external request from GatewayClass and listeners through Route attachment, TLS, cross-namespace trust, and backend selection.
Follow a web app calling an API: start with a Pod, add a Service, then decide how traffic enters and who may connect.
Follow a connection from a stable Service address through EndpointSlices, proxy rules, traffic policy, and a changing set of backend Pods.
Follow a Pod from sandbox creation through CNI attachment, address allocation, same-node and cross-node forwarding, cleanup, and diagnosis.
Try a broader term or clear one of the filters.