k8s-istio-troubleshooting
Istio troubleshooting
Find out why requests fail or behave unexpectedly in an Istio mesh, 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.
In sidecar mode every meshed pod has an Envoy container, istio-proxy, injected when
its namespace has istio-injection=enabled (or an istio.io/rev label). The client's
sidecar routes by VirtualServices and DestinationRules (subsets, load balancing,
TLS); the server's sidecar enforces PeerAuthentication (mTLS) and
AuthorizationPolicies. Each sidecar writes an access log line per request with a
response flag that says what Envoy did. In ambient mode the node's ztunnel
handles L4 and mTLS and an optional waypoint proxy handles L7.