k8s-envoy-troubleshooting
Envoy troubleshooting
Find out why Envoy does not pass a request on, 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.
Envoy takes a request on a listener, matches a route by the Host header
(domains) and the path, and sends it to a cluster, whose hosts come from DNS
(STRICT_DNS, LOGICAL_DNS), a static list or a control plane (EDS). When it cannot,
it answers itself and records why: in the access log as a response flag (UH,
UF, NR ...) and %RESPONSE_CODE_DETAILS%, and in its stats. A standalone Envoy reads
its bootstrap once at start, so a config error stops it and an edited ConfigMap needs a
restart.