Service Mesh Platform  ·  View 28 of 31  ·  6 · Operations

Progressive Delivery Cycle

The six steps every release runs through, and the evidence that moves it from one to the next.

Editable source SVG draw.io All views
Declare subset version label Mirror idempotent only Cohort header match Weight step 1 → 5 → 25 → 50% Read effective mesh-reported share Decide promote or revert Release pods ready no diffs staff pass applied analysis next release Progressive Delivery — The Loop Every Release Runs Application we own Interface / broker Data store Decision point v 1.0 · owner Platform Networking Architecture · date 2026-09

Decisions

  • Mirror before cohort, cohort before percentage. Each step exposes the new version to a larger and less forgiving audience, and each can be skipped by a declared exception, not by habit.
  • The step that reads the applied share is part of the loop, not a debugging tool. It is what turns 'we set 1%' into 'the mesh sent 0.98%'.

Targets

  • Weight granularity 1%. Revert is the fastest operation in the loop, and is measured on every abort.

Deliberately out

  • Traffic mirroring of non-idempotent methods, and header-based cohorts built on user-supplied headers that the edge does not strip.
◀  Roadmap All views Security — Trust Zones  ▶
Solution Architecture v1.0 · Platform Networking Architecture · 2026-09 · 31 views · open source, fully on-premises28-progressive-delivery-cycle