k8s-envoy-troubleshooting

Use when an Envoy proxy on Kubernetes fails requests: clients get 503 "no healthy upstream", 503 "upstream connect error or disconnect/reset before headers. reset reason: remote connection failure", 404 with an empty body, or 504 "upstream request timeout", access logs show response flags (UH, UF, NR, NC, UT, UO, URX, UC), or Envoy crashes at start ("has unknown fields", "no such field", "route: unknown cluster"). Covers Envoy run directly (a Deployment with its own bootstrap, a front proxy, a sidecar) and the proxy under Contour, Emissary or Gloo; reads the access log, the bootstrap and Envoy's read-only admin endpoints. Investigates with kubectl get and logs, and proposes fixes. Reads first and asks before changing anything.

License

Apache-2.0