Separate workload and flag decisions

Separate workload and flag decisions A workflow diagram generated by Archify. 01 / Infrastructure level: traffic split (Flagger) 02 / Application level: feature flag EX / Failure response · separate recovery Deploy Canary traffic Metric analysis Progressive rollout Full release Deploy new version · Feature flag off · Infrastructure level: traffic split (Flagger) › Deploy Deploy new version Feature flag off Canary release · small share of traffic · Infrastructure level: traffic split (Flagger) › Canary traffic Canary release small share of traffic Metric analysis · error rate · latency · Infrastructure level: traffic split (Flagger) › Metric analysis · interval 1m Metric analysis error rate · latency interval 1m Expand traffic · example: 10 → 50% · Infrastructure level: traffic split (Flagger) › Progressive rollout Expand traffic example: 10 → 50% Workload promoted · deployment analysis passed · Infrastructure level: traffic split (Flagger) › Full release Workload promoted deployment analysis passed Limited exposure · trusted app context · Application level: feature flag › Canary traffic · separate Git change Limited exposure trusted app context separate Git change Expand targets · separate cohort validation · Application level: feature flag › Progressive rollout Expand targets separate cohort validation Approve exposure · separate flag decision · Application level: feature flag › Full release Approve exposure separate flag decision Flag cleanup · consumers / rollback · Application level: feature flag › Full release Flag cleanup consumers / rollback Workload recovery · inspect surviving traffic · Failure response · separate recovery › Metric analysis · flag is separate Workload recovery inspect surviving traffic flag is separate Restore flag config · separately approved change · Failure response · separate recovery › Full release Restore flag config separately approved change separate PR separate approval pass failure limit separate change Legend Code deployment Flag control (flagd) Analysis gate / rollback Traffic split (Flagger)

Analysis gate (Canary.spec.analysis)

  • • threshold 5: cumulative failed-check limit
  • • Example policy: success ≥99%, latency ≤500ms
  • • Verify instrumentation and sample volume

Independent flag decision

  • • Promotion does not automatically change flag exposure
  • • A successful rollback hook requests workload rollback
  • • Flag restoration and consumer freshness are separate