Argo Rollouts helps release a new application version without sending every user to it immediately. A canary rollout exposes a small share of traffic first; a blue-green rollout keeps two versions ready before switching between them. The controller manages those steps and can use measurements to decide whether to proceed. It is useful when releasing gradually and stopping a bad change are important parts of your deployment process.
Deployment and operating notes
Argo CD can deliver the declarations, while the Rollouts controller manages the rollout behavior.
Chart ownership
The Argo Rollouts installation documentation links to the community-maintained argo-helm charts. The argo-rollouts chart is distributed through https://argoproj.github.io/argo-helm. Treat the community chart and the controller release as related artifacts with their own configuration and upgrade notes.
Before adoption
Verify integration with the exact traffic router and metrics provider you operate. An application Helm chart must declare Rollout resources for the controller to act on them. Define analysis thresholds and an abort path, including database compatibility when old and new application versions overlap. Prevent a second controller or manual deployment process from independently changing the same rollout resources.
Read the installation guidance and application Helm integration documentation.
Sources & further reading
Spotted something that needs another look?
Help improve this page →