| 503 errors begin right after a DestinationRule is applied and stop when it is reverted | The Envoy response flag in the istio-proxy access log (kubectl logs <pod> -c istio-proxy; flags sit after the response code, UF means the upstream connection failed); the DestinationRule's trafficPolicy.tls.mode against the mesh-wide mTLS setting, because an unset mode defaults to DISABLE and the client sidecar sends plain HTTP to a server that expects TLS. | Set trafficPolicy.tls.mode to ISTIO_MUTUAL wherever mTLS is on, or scope the rule to the workloads it was written for, and add the change to a pre-merge istioctl analyze run. |
|---|
| 503 UC when a client reaches StatefulSet pods by pod IP under STRICT mTLS | Whether the Service is headless (clusterIP: None), the port name (http-web against tcp-web) and the Host header the client sends; the sidecar on the server side finds no route entry for a request that arrived through the passthrough cluster. | Send the right Host header, address pods by their stable DNS names, or name the port tcp-<name> so only the TCP proxy filter is used. |
|---|
| New pods fail to start with a failed calling admission webhook error from sidecar-injector.istio.io, or start without a sidecar | The caBundle of the MutatingWebhookConfiguration against the root certificate mounted in the istiod pod (x509: certificate signed by unknown authority points to an empty or stale one); the webhook's namespaceSelector; whether the namespace carries both istio-injection and istio.io/rev, since istio-injection wins. | Repair the caBundle, relabel the namespace to one label, remove a leftover injector webhook from the old control plane, and restart the workloads to re-inject. |
|---|
| A route or policy change is not taking effect on some workloads | istioctl proxy-status for SYNCED, NOT SENT and STALE per proxy (STALE means istiod sent an update and got no acknowledgement); istioctl proxy-config listeners, routes, clusters and endpoints on the pod that misbehaves; istioctl analyze --all-namespaces for the resource. | Fix the connection or resource that keeps the proxy out of sync, then confirm the proxy-config output matches the intended route before closing. |
|---|
| Ingress gateway returns 404, or health checks pass while real traffic fails | Gateway tls.mode (SIMPLE or PASSTHROUGH) against whether the VirtualService uses http or tls routing, via istioctl proxy-config routes and listeners; two Gateways sharing one wildcard certificate, which makes HTTP/2 browsers reuse a connection and receive 404; a cloud load balancer that terminates TLS without forwarding SNI. | Match the routing type to the Gateway's TLS mode, merge to a single wildcard Gateway, or pass TLS through or set hosts to * where SNI is lost. |
|---|
| Requests denied or allowed that should not be after an AuthorizationPolicy change | istioctl x authz check <pod>.<namespace>, then istioctl proxy-config log deploy/<name> --level rbac:debug to read the rules the proxy evaluated; a stray list item that created a second, broader rule; HTTP-only fields such as host or path on a TCP port, which make the policy match nothing or deny everything. | Correct the rule structure, name the Service port with its protocol, test against a canary workload and keep the previous policy as the way back. |
|---|
| An EnvoyFilter that worked stopped applying after an Istio upgrade | Whether it uses INSERT_BEFORE or INSERT_AFTER relative to a built-in filter such as istio.stats, which is ignored with nothing in the log when the target filter is newer; whether its match includes proxyVersion, so the filter it patched was replaced. | Use an operation that does not depend on another filter, such as INSERT_FIRST, or set an explicit priority, and keep an inventory of EnvoyFilters before each upgrade. |
|---|
| Ambient namespace: traffic fails between pods after the namespace joined the mesh | istioctl ztunnel-config workloads and certificates for the ztunnel on each node, ztunnel logs (kubectl -n istio-system logs -l app=ztunnel) for the connection, and whether an L7 AuthorizationPolicy or route is targeting a namespace that has no waypoint. | Add a waypoint for the namespace or retarget the policy, confirm the workloads and certificates appear in ztunnel, then re-test the path. |
|---|