Edge Cache and CDN Platform  ·  View 23 of 29  ·  6 · Operations

Change Pipeline

How a property change or a Traffic Server upgrade reaches production, and the gates that can stop it.

Editable source SVG draw.io All views
Propose Merge request Forgejo Two reviewers owner + platform Validate CUE schema types · defaults Identity in key? invariants Identity probe two test users Build Compile bundle Envoy + ATS + keyspec Sign cosign · key in OpenBao Canary Canary PoP 1 PoP · 10 min bake Regression? 5xx · hit · stale Widen Region ring 1 continent · 20 min Global ring all PoPs · 60 s push Undo Revert pointer to previous rejected, line named Change Pipeline — Configuration and Software Take the Same Road Security / platform Application we own Decision point Risk / gap failure / alternate A Traffic Server or Envoy upgrade ships as a signed image through the same rings and the same regression gate. v 1.0 · owner Edge Platform · date 2026-09

Decisions

  • Validation has three layers: CUE for types and defaults, invariants such as 'a rule marked identity-varying must name the identity in its key', and a differential probe that fetches declared test URLs as two test users and compares the bodies.
  • Bundles are compiled once, signed with a key held in OpenBao, and addressed by hash. A PoP applies a bundle only if the signature checks against the platform's public key, so a compromised object store cannot push configuration.
  • Software upgrades go through the same rings and the same regression gate. A new Traffic Server version is a new image hash, not a special process.

Numbers

  • Standard change: 10-minute canary bake, 20-minute region bake, then global. An emergency revert skips the bakes.

Risks

  • The identity probe only covers URLs the owner declares as test URLs. A property with poor test URLs gets weaker protection. The per-path Vary-mismatch alert in production is the second line.