Services and Service Discovery

Your application calls productcatalogservice:3550. There's no host file entry, no config file, no hardcoded IP behind that name. The Pod answering that request might not have existed five minutes ago. How does this work?

Two mechanisms working together: Services provide stable network endpoints that survive Pod restarts and scaling, and CoreDNS makes those endpoints discoverable by name. This article covers how Services map DNS names to Pods, the four Service types that control where endpoints are reachable from, and the DNS plumbing that ties it all together.