Kubernetes / Services, DNS & Traffic Routing
Find an Ingress ignored by the intended controller
An Ingress can exist without a controller handling it because its class or controller assignment is wrong.
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 get ingress web -o yaml
kubectl get ingressclassRead the result
The Ingress class reference and installed classes describe intended ownership. A controller's implementation and configuration determine what it actually processes.
Resolve and verify
Compare ingressClassName with the supported installed controller and its events or logs. Correct the managed ownership and verify the resulting route.
Before changing production
Do not install a second controller or change the default class without assessing other Ingress resources.