Service Mesh Platform · View 21 of 31 · 5 · Runtime
Decisions
- Proxies keep their last acknowledged configuration indefinitely. There is no staleness timer, because the certificate already bounds how long a proxy can run alone and a second timer would only fail first.
- A crashed proxy does not come back until istiod does. Envoy keeps configuration in memory, and persisting xDS to disk would mean forking the proxy agent. The pod goes unready and its peers carry its share.
- An emergency deny during the outage is a Cilium network policy. It is coarse and it does not depend on istiod.
The promise, stated plainly
- Existing traffic: no degradation for 12 h. Between 12 and 24 h, renewals fail and pages fire while traffic still flows. Beyond 24 h, pods whose certificates expire fail closed one by one.
Deviation from the requirement
- The requirement asks that a crashed proxy restart from a local config cache. This design does not provide that during a total outage, and says so: the cost is the pods that crash in that window, and the alternative is maintaining a fork of the mesh's agent indefinitely.