Why Separating Identity from Location Is the Key Principle Behind DNS and Kubernetes

A foundational concept in networking and distributed systems holds that identity—who something is—and location—where it can be reached—are distinct pieces of information that must not be conflated. Common examples illustrate the difference: a passport identifies a person regardless of where they travel, while a house address is a location because it changes when someone moves and can be shared by multiple people. Whenever identity and location differ, a third element called a mapping is required to link the two, as seen in phone contacts, Google Maps, and company employee records. DNS functions precisely as this kind of mapping, translating a stable domain name like google.com into a changeable IP address. Kubernetes applies the same principle through its Service abstraction, which provides a stable endpoint in front of pods whose IP addresses change constantly.