Debugging a Broken Ingress Setup: A Step-by-Step Walkthrough

A Kubernetes Ingress setup stopped working after changes were made to the cluster, including installing a different CNI. The issue was tracked down by ruling out DNS, firewall, and service problems. The final diagnosis was that 10.96.101.127, the ClusterIP, is not a real network address, but a virtual IP used by Kubernetes. Engineers should be aware of this when debugging Ingress issues.