Cheat notes · Module 01 · Foundations
Install Argo Rollouts from Git
A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.
The idea
Argo Rollouts is a controller with its own resource, the Rollout: a Deployment's pod template plus a strategy. It is installed like every other add-on in the platform: one Application in apps/, a pinned chart version and values in Git, never a kubectl apply of a release URL.
Remember
- Pinned: chart
argo-rollouts2.43.12, controller v1.10.2. Upgrades are a pull request changing that line. - ServerSideApply: the Rollouts CRDs are too large for a client-side apply's annotation.
- Sync wave -1: the CRDs exist before any app that uses a Rollout.
- Dashboard read-only: it shows every Rollout; promote and abort go through Argo CD or the CLI, so they leave a trace.
- kubectl plugin:
kubectl-argo-rolloutson your PATH giveskubectl argo rollouts ....
Pitfalls
- Installing from the latest manifest URL. The version changes under you; pin the chart.
- A client-side sync of the CRDs fails with
metadata.annotations: Too long. UseServerSideApply=true.
Commands
argocd app wait argo-rollouts --sync --health | Wait for the controller |
kubectl get crd -o name | grep argoproj.io | Rollout, AnalysisTemplate, AnalysisRun and the rest |
kubectl argo rollouts list rollouts -A | Every Rollout (none yet) |
kubectl -n argo-rollouts port-forward svc/argo-rollouts-dashboard 3100:3100 | The dashboard at localhost:3100/rollouts |
Test yourself
Answer in your head first, then open the answer.
Why does the Rollouts Application run in wave -1?
So its CRDs exist before any app that contains a Rollout is synced.
Why is the dashboard read-only?
Releases are changed through Argo CD or the CLI, which have RBAC and leave a trace.
How do you upgrade Argo Rollouts?
A pull request that changes the pinned chart version in its Application.
Where module 01 leaves you: Argo Rollouts v1.10.2 runs in the argo-rollouts namespace, installed from your platform repo. Nothing uses it yet: checkout is still a Deployment.