k8s-envoy-gateway-troubleshooting
Envoy Gateway troubleshooting
Find out why Envoy Gateway does not route a request, and propose a fix. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
A GatewayClass with controller gateway.envoyproxy.io/gatewayclass-controller
belongs to Envoy Gateway. For each Gateway of that class, Envoy Gateway runs an
Envoy Deployment and Service (by default in envoy-gateway-system, labelled
gateway.envoyproxy.io/owning-gateway-name). HTTPRoutes (and GRPC, TLS, TCP and UDP
routes) attach to a Gateway's listeners and send traffic to backends. Every object
reports what Envoy Gateway made of it in its status conditions, so the status usually
names the cause. Envoy Gateway's own policies (BackendTrafficPolicy,
ClientTrafficPolicy, SecurityPolicy, EnvoyProxy, EnvoyPatchPolicy)
attach to Gateways or routes.