Rollouts¶

A rollout binds a Published configuration version to a target group and a strategy. The rollout walks through batches, watches health gates, and (in the bad case) pauses or rolls back.

Lifecycle (recap)¶

stateDiagram-v2
    [*] --> Pending
    Pending --> InProgress: start
    InProgress --> Paused: gate / operator
    Paused --> InProgress: resume
    InProgress --> Completed: all batches succeeded
    InProgress --> Failed: aborted by operator or gate
    Failed --> RolledBack: rollback to last stable
    Completed --> [*]
    RolledBack --> [*]

Choosing a strategy¶

• Batch — small fleets, manual control, deliberate pace.
• Percentage — large fleets, automated pacing, manually advanced between steps.
• Canary step-up — the safest default for production. Percentages with time-based dwell between steps; an operator only intervenes when a gate fires.

Mixed groups (different agent versions or environments) are fine; the rollout engine treats them uniformly. Capability gating means an agent that does not advertise AcceptsRemoteConfig is silently skipped with an explanatory chip.