Kubernetes / Services, DNS & Traffic Routing
Inspect Gateway API acceptance and routing status before blaming a backend
Gateway API resources require installed APIs and a supporting controller. A route can exist but be rejected or fail reference resolution.
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 httproute web -o yamlRead the result
On a cluster with the applicable Gateway API CRDs, inspect parent status conditions such as acceptance and resolved references. API versions and controller capabilities vary.
Resolve and verify
Compare parent references, allowed routes and backend references with the installed implementation's documentation. Correct the demonstrated attachment or reference failure and retest.
Before changing production
Do not assume Gateway API is automatically installed or equivalent to every Ingress annotation behavior.