A school district app resolves short name api inside its own namespace but fails when the same short name is used to reach a Service in another namespace. Why?
Select an answer to reveal the explanation.
Short Explanation
Short name api is like saying “front desk” on your own floor—search paths fill in your namespace. Another floor needs a clearer address, such as api.otherns or the full svc.cluster.local name.
Full Explanation
Pod DNS search domains expand unqualified names within the current namespace context. A short name that works locally will not uniquely identify a Service in another namespace; clients should use service.namespace or the FQDN. NetworkPolicy, Service type, and headless vs ClusterIP do not create cross-namespace short-name magic.