How does Kubernetes solve the same service-discovery problem Compose solves with embedded DNS?

A Kubernetes Service is assigned a stable virtual IP and DNS name (via CoreDNS) that load-balances across the current set of healthy Pods backing it, regardless of how often individual Pod IPs change as Pods are recreated. This is the direct cluster-scale analog of Compose's embedded DNS resolving service names to container IPs (Chapter 5/6) — the underlying problem (stable names over unstable individual instances) and the DNS-based solution are conceptually identical.