Service Mesh Platform  ·  View 14 of 31  ·  4 · Data

Configuration Distribution Pipeline

The seven steps from a merged change to a configuration every affected proxy has acknowledged, and the check that closes the loop.

Editable source SVG draw.io All views
Author Intent change one of three repos Check Schema + lint timeout required Impact replay 24 h of access logs Package Rendered bundle OCI · cosign Apply Argo CD wave canary cluster first Admission guards second line Compile istiod scoped per workload Deliver Envoy sidecar delta · ACK or NACK Verify Drift exporter sha per proxy halt wave Configuration Distribution — From Merge to Acknowledged Data store Decision point Application we own Security / platform Interface / broker failure / alternate A push is finished when proxies acknowledge it and the drift exporter sees the new sha, not when Argo CD reports Synced. v 1.0 · owner Platform Networking Architecture · date 2026-09

Decisions

  • The impact check replays the last 24 hours of access logs against a proposed authorisation change and reports what it would have denied. Above 0.5% of a service's traffic the merge needs an explicit override from the security repository's owners.
  • istiod sends deltas: a one-route change reaches only the proxies whose scope includes that route, and only that route. Scope comes from declared dependencies.
  • A push is done when the drift exporter sees the new sha on the affected proxies. Argo CD reporting Synced means the object is in etcd, which is not the same thing.

Targets

  • Intent accepted to effective on 95% of affected proxies: p95 ≤ 5 s, p99 ≤ 15 s.

Risks

  • Delta xDS introduces a class of bug where a proxy silently diverges from intent. The drift exporter compares acknowledged sha per proxy, and a proxy stale for more than 60 s is forced to resubscribe.