Kubernetes / Services, DNS & Traffic Routing
Investigate an Ingress returning the wrong route or a 404
A host or path can miss its intended rule even while the controller and backend are healthy. Inspect the exact routing definition.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app describe ingress webRead the result
Rules, path types, backend references and events help explain controller routing. Rewrite annotations and matching behavior can be implementation-specific.
Resolve and verify
Compare the real request hostname and path with the intended rule and controller documentation. Correct the narrow mismatch and validate both expected and neighboring routes.
Before changing production
Do not add a broad catch-all rule that accidentally exposes unrelated backends.