DevOps · Flashcard

After a rollout every Pod has a new IP. What does a Service add?

  • AOne virtual IP and DNS name that always routes to whichever Pods exist now
  • BOne fixed IP per Pod, which that Pod keeps across restarts and rescheduling
  • COne DNS record per Pod, which the kubelet updates as Pods come and go
  • DOne proxy Pod that holds client connections open while the others restart

Why this is the answer

A Service is a stable front door: its ClusterIP and DNS name never change, while the set of Pods behind it is recalculated from a label selector as Pods appear and disappear. Pod IPs themselves are never stable — a restarted Pod gets a new one. Per-Pod DNS exists only for headless Services, and no proxy Pod is created; the routing lives in each node's packet rules.

Official docs
Study in Gnoseed →