Problem: There's no way today to stage a new version across a fleet of instances, target a rollout at one customer, or roll one back without affecting others — every self-hoster pulls the same image tag from the same release channel.
Area: ORB / Fleet ops
Proposal: Design and build a rollout mechanism that can target a specific instance or subset of instances with a specific version, independent of the default release channel.
Deliverables:
- A working, documented targeted-rollout mechanism.
Acceptance criteria:
AMS Cloud Readiness cross-reference (added 2026-07-12)
See also #5222 in the new AMS Cloud Readiness milestone (#28) — the AMS-side parallel to this exact problem, already citing this issue as precedent. Keep both sides in sync if either design changes.
Problem: There's no way today to stage a new version across a fleet of instances, target a rollout at one customer, or roll one back without affecting others — every self-hoster pulls the same image tag from the same release channel.
Area: ORB / Fleet ops
Proposal: Design and build a rollout mechanism that can target a specific instance or subset of instances with a specific version, independent of the default release channel.
Deliverables:
Acceptance criteria:
AMS Cloud Readiness cross-reference (added 2026-07-12)
See also #5222 in the new AMS Cloud Readiness milestone (#28) — the AMS-side parallel to this exact problem, already citing this issue as precedent. Keep both sides in sync if either design changes.