Services

Part of the Kubernetes course

You have a Deployment keeping three Pods alive, which solves the problem of Pods dying and not coming back. It does not solve a second problem that shows up the moment you try to actually talk to those Pods: every Pod has its own IP address, and that address is not something you can rely on. A Pod that crashes and gets replaced comes back with a brand new IP.

What you actually want is one address that never changes, no matter how many Pods are behind it or how often they get replaced. That is what a Service is: a stable name and a stable virtual IP that quietly spreads traffic across whatever Pods currently match a label selector, the same kind of selector you already used in the last lesson to let a Deployment find its own Pods. ...