A library frontend in namespace web cannot resolve a backend Service named catalog in namespace data using only the short name catalog. What DNS name should it use instead?
Select an answer to reveal the explanation.
Short Explanation
Short Service names only work inside the same namespace—cross-namespace needs the fuller name, like catalog.data.svc.cluster.local. Think city, street, then house number.
Full Explanation
CoreDNS resolves short Service names within the Pod's namespace search path. Reaching a Service in another namespace requires a qualified name of the form <service>.<namespace>.svc.cluster.local (or an equivalent partial qualification). Hard-coding node /etc/hosts or assuming default namespace names will not correctly address the Service in data.