An open-data client in namespace analytics calls a short Service name that exists in both analytics and shared namespaces and resolves incorrectly. What DNS pitfall is involved?
Select an answer to reveal the explanation.
Short Explanation
Short names are like yelling “Alex” in a crowded hallway—DNS search paths decide which Alex answers. Cross-namespace calls need the full name on the mailbox.
Full Explanation
Pods append DNS search domains (including their namespace). An unqualified Service name may resolve to a different namespace’s Service than intended. Identical names across namespaces are allowed. Prefer FQDNs such as my-svc.other-ns.svc.cluster.local for explicit cross-namespace targeting.