Service Mesh Platform · View 24 of 31 · 6 · Operations
Decisions
- The control plane is never upgraded in place. The new istiod revision runs beside the old one; a namespace moves by changing its revision tag, and its pods restart onto the new proxy.
- Each proxy talks to the istiod of its own revision. Version skew is held in both directions by construction rather than by trusting cross-version compatibility.
- Abort is a retag and a rolling restart back. Stopping mid-way is a supported state that can last weeks.
Targets
- One minor version of skew in each direction at any time. Upgrades at least quarterly, so the fleet never falls outside the upstream support window.
Risks
- Restarting 40,000 pods is itself a load event on SPIRE and istiod. Waves are rate-limited to the issuance headroom of 2,000 a second per cluster and gated on PodDisruptionBudgets.