Cheat notes · Module 08 · Operate
Operate releases with teams
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
The product team owns its releases, so it needs the buttons for them and nothing more. Argo CD resource actions give resume, abort and retry on Rollouts under Argo CD's RBAC, with a trace. Notifications tell the team when a release finishes or aborts, a deadline aborts a release that is stuck, and a runbook says who does what.
Remember
- RBAC:
action/argoproj.io/Rollout/resume,abortandretryforrole:checkout-teamoncheckout/*, instead ofaction/*. argocd app actions run APP resume --kind Rolloutis promote through Argo CD;restartis denied for the team.- Notifications in the Rollouts values: a webhook service
release-log, templates and triggerson-rollout-completedandon-rollout-aborted. - Subscriptions are annotations on the Rollout:
notifications.argoproj.io/subscribe.on-rollout-aborted.release-log. progressDeadlineAbort: true: a release that makes no progress for the deadline aborts instead of hanging.docs/releases.md: who promotes, who aborts, how to revert, where the checks are.
Pitfalls
- Giving the team
action/*: it can then restart or delete pods of any kind in its apps. - A notification that never arrives because the Rollout has no subscription annotation. The trigger alone sends nothing.
Commands
argocd app actions list checkout-prod --kind Rollout | What the team may run |
argocd app actions run checkout-prod resume --kind Rollout | Promote through Argo CD |
argocd app actions run checkout-prod abort --kind Rollout | Abort through Argo CD |
kubectl -n release-log logs deploy/release-log -f | Every notification, as it arrives |
argocd-platform platform/argocd/values.yaml (RBAC excerpt)
p, role:checkout-team, applications, action/argoproj.io/Rollout/resume, checkout/*, allow
p, role:checkout-team, applications, action/argoproj.io/Rollout/abort, checkout/*, allow
p, role:checkout-team, applications, action/argoproj.io/Rollout/retry, checkout/*, allow
Test yourself
Answer in your head first, then open the answer.
How does the product team promote without kubectl access?
argocd app actions run checkout-prod resume --kind Rollout, allowed by its RBAC role.
What makes a notification go to the release log?
A trigger and template in the Rollouts values, and a subscription annotation on the Rollout.
What does progressDeadlineAbort prevent?
A release that hangs forever half-done; it aborts after the progress deadline.
Where module 08 leaves you: The checkout-dev account can resume, abort and retry checkout's Rollouts and nothing else. Every completed or aborted release writes a line to the release log. Prod runs 6.13.0. docs/releases.md is in your platform repo.