Edgaras
@apsega.bsky.social
CNCF Ambassador / Kubestronaut / Cloud Native Lithuania meetup organiser / apsega.lt
Apparently there's no way of sharding Istio control plane. In my case, having 2 Kubernetes clusters (with 600+ physical nodes) in multi-primary Istio setup resulted up to 700(!) CPU cores usage for Istiod.
Luckily, you can see when `PILOT_DEBOUNCE_AFTER` was increased to 1s (default: 100ms).
Luckily, you can see when `PILOT_DEBOUNCE_AFTER` was increased to 1s (default: 100ms).
January 10, 2025 at 11:37 AM
Apparently there's no way of sharding Istio control plane. In my case, having 2 Kubernetes clusters (with 600+ physical nodes) in multi-primary Istio setup resulted up to 700(!) CPU cores usage for Istiod.
Luckily, you can see when `PILOT_DEBOUNCE_AFTER` was increased to 1s (default: 100ms).
Luckily, you can see when `PILOT_DEBOUNCE_AFTER` was increased to 1s (default: 100ms).