A 911 platform observes that Endpoints already list new Pod IPs after a rollout, yet a few connections still hit old backends for a short time. What should the administrator understand?
Select an answer to reveal the explanation.
Short Explanation
The directory can update before every hallway router gets the memo — Endpoints lead, kube-proxy/dataplane follows, sometimes with a short lag.
Full Explanation
Endpoint and EndpointSlice updates are consumed by kube-proxy or alternative dataplanes that program iptables, IPVS, eBPF, or equivalent rules. Propagation is eventually consistent at human-visible timescales, so brief stale forwarding can appear after Pod moves. etcd does not remote client sockets; CoreDNS is not the Pod IP load-balancing plane for ClusterIP Services.