Progressive Delivery

Skyflo exposes 13 Argo Rollouts tools via MCP. Status monitoring is read-only. Delivery control operations (pause, resume, promote, cancel, abort) require explicit approval.

Workflow: Status Monitoring

Get rollout status, list rollouts. Read-only. No approval required.

Use status to understand where a rollout is in its progression before deciding to promote, pause, or abort.

Workflow: Delivery Control (Approval-Gated)

Pause, resume, promote, cancel. Each operation affects live traffic. Approval required.

Promote is the critical gate. Moving canary traffic to stable is a production decision. The agent proposes; you approve.

Workflow: Abort (Destructive)

Abort a rollout entirely. Reverts to the previous stable version. Destructive. Flagged. Approval required.

Abort is annotated as destructive. Use when a canary is failing and you need to cut over immediately. The UI flags it.

Integration with Approval Gates

Argo Rollouts control traffic. A bad promote can send 100% traffic to a broken canary. Skyflo's approval gate ensures:

1. Agent proposes promote (or pause, resume, abort).
2. UI shows the pending operation and current rollout state.
3. You approve or deny.
4. Execution proceeds only on approval.

No autonomous promotions.

Example Workflows

"What is the status of the api rollout?"

1. Agent gets rollout status.
2. Returns phase, steps, canary weight, stable replicas.
3. No approval (read-only).

"Promote the frontend canary to 50%"

1. Agent finds the rollout, determines next step.
2. Proposes promote.
3. Pauses for approval.
4. Executes on approval. Verifies new status.

"Abort the payments rollout, it is failing"

1. Agent finds the rollout.
2. Proposes abort. Flagged as destructive.
3. Pauses for approval.
4. Executes on approval. Reverts to previous stable.

Safety Summary