> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usekestrel.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Argo Rollouts

> Connect Argo Rollouts for progressive delivery actions — promote, abort, retry, and roll back canary and blue-green rollouts in workflows

The Argo Rollouts integration connects Kestrel to your in-cluster Argo Rollouts installation, enabling AI agents to promote canary deployments, abort or retry failed rollouts, and roll back to previous revisions as part of automated workflows and incident response.

## Prerequisites

* Kestrel Operator deployed in your cluster (see [Kubernetes](https://docs.usekestrel.ai/integrations/kubernetes.md))
* Argo Rollouts controller and CRDs installed in the same cluster (`argoproj.io/v1alpha1 Rollout`)

## Setup

Argo Rollouts is auto-detected by the Kestrel Operator when the Rollout CRD is present in the cluster. No manual connection or credentials are required.

**1. Install Argo Rollouts**

If Argo Rollouts is not already installed:

```bash theme={null}
kubectl create namespace argo-rollouts
kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/latest/download/install.yaml
```

**2. Verify detection**

The operator probes for the Rollout CRD periodically. Check the operator logs:

```bash theme={null}
kubectl logs -n kestrel-ai deploy/kestrel-operator | grep -i "Rollouts"
```

Once detected, the integration shows as **Detected** on the Integrations page and Rollouts action blocks become available in the workflow builder.

> [!NOTE]
>
> The integration is enabled by default. To opt out, set `operator.rollouts.enabled: false` in your Helm values and upgrade the operator (this sets `ROLLOUTS_DISABLED=true` on the operator deployment).

## How It's Used

### In Workflows

**Action blocks:**

* **Promote Rollout** — promote a paused canary/blue-green rollout to the next step (or fully with `full: true`)
* **Abort Rollout** — abort an in-progress rollout and revert to the stable version
* **Retry Rollout** — retry an aborted rollout from the beginning
* **Rollback Rollout** — roll back a rollout to a previous revision (defaults to the last revision)
* **Pause Rollout** / **Resume Rollout** — pause or resume rollout progression
* **Restart Rollout** — restart the pods of a rollout without changing the version
* **Get Rollout Status** — retrieve current phase, step, and canary weight of a rollout
* **Wait for Rollout Healthy** — block workflow execution until a rollout reports Healthy (with configurable timeout)

Example: A workflow triggered by a Datadog monitor alert on elevated error rates uses "Abort Rollout" to stop the in-progress canary, then posts the rollout status to Slack for the on-call engineer.

### Scoping

Rollout actions are scoped by **cluster**, **namespace**, and **rollout name** — all populated with dropdowns from live cluster data in the workflow builder.

## Disconnecting

To disable the Argo Rollouts integration, set the following in your Helm values and upgrade the operator:

```yaml theme={null}
operator:
  rollouts:
    enabled: false
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.