Kubernetes Service

Problem

Pods are temporary. Today your API might be: 10.2.1.17 Tomorrow Kubernetes replaces it: 10.2.4.91 Clients can't depend on pod addresses.

Solution — Kubernetes Service

A Service provides a stable logical endpoint for a changing set of pods. 
           ┌→ Pod A
api-service → Pod B
           └→ Pod C
Core idea: Services separate stable service discovery from ephemeral pod identities.