EnvoyIstio

Large xDS configuration updates cause CPU spikes

warning
configurationUpdated Feb 24, 2026(via Exa)
How to detect:

When istiod pushes xDS configuration updates, every affected sidecar parses and applies the configuration. Large configurations with many services and routes cause significant CPU consumption during updates and increase baseline CPU for route matching evaluations.

Recommended action:

Use Sidecar resource to limit egress configuration scope to only necessary namespaces and services. Set spec.egress.hosts to ['./*', 'istio-system/*'] to receive only configuration for services in the same namespace and istio-system. Reduces config processing CPU and route evaluation overhead.