County in-cluster Service DNS works, but browsers on the public Internet cannot resolve the Ingress hostname. Where is the gap?
Select an answer to reveal the explanation.
Short Explanation
CoreDNS is the office directory; public DNS is the phone book on the Internet. In-cluster names can be perfect while the world’s DNS entry for your Ingress host is still missing.
Full Explanation
CoreDNS serves cluster-local names. External clients need public DNS (or another external resolution path) pointing the Ingress hostname at the entrypoint address. kube-proxy restarts, ClusterIP auto-registration on the Internet, and Pods publishing root glue are not how external hostname resolution works.