Configure an Argo Rollouts canary strategy with setWeight and pause steps to progressively shift traffic to a new model-serving version
domain: argo-rollouts.readthedocs.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Convert the Deployment to a Rollout resource with `strategy.canary.steps`, alternating `setWeight: <percent>` and `pause` entries
Reference dedicated `canaryService` and `stableService` Services so each version can be targeted independently by traffic tooling
Set `pause: { duration: <n><s|m|h> }` for timed pauses, or `pause: {}` to pause indefinitely until manually promoted
Manually advance an indefinite pause with `kubectl argo rollouts promote <rollout>`
Tune `maxSurge`/`maxUnavailable` if you need to control how many extra pods are created during the shift
Known gotchas
Without a traffic router configured, Argo Rollouts approximates the requested setWeight by scaling ReplicaSet replica counts (best-effort rounding), not by exact percentage-based traffic splitting — use `trafficRouting` for fine-grained control at low replica counts
If `steps` is omitted entirely, the canary strategy just mimics a plain rolling update
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?