Cheat notes · Module 00 · Foundations
Orientation: deploy is not release
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
Deploying is not releasing. Argo CD makes the cluster match Git, and a Deployment then replaces every pod as soon as each one is ready, so every user meets a bad version at once. Progressive delivery runs the new version first and gives it users a share at a time, while metrics or a person decide whether it goes on.
Remember
- Deploy: new pods run. Release: users reach them. Progressive delivery puts time and a decision between the two.
- Blue-green: a full copy of the new version behind a preview, then one switch for everyone. Fast to undo, double the pods for a while.
- Canary: a share of the users first, more in steps, judged at each step. Fewer extra pods, slower to finish.
- Owners: the platform team runs the controller, Prometheus, the mesh and the shared checks. The product team owns its release steps in
checkout-config. - Same setup as the Argo CD course: kind cluster,
argocd-platform,checkout-app,checkout-config, alice for the platform.
Pitfalls
- Starting on a broken Argo CD platform. Fix or rebuild it first: every module assumes it is Synced and Healthy.
- Thinking a readiness probe judges a release. It only says the pod answers, not that its answers are right.
Commands
kubectl argo rollouts version | Is the plugin installed? |
argocd app list | Every Application, Synced and Healthy before you start |
kubectl -n checkout-dev get deployment checkout -o jsonpath='{.spec.strategy}' | How a release goes out today (RollingUpdate) |
Test yourself
Answer in your head first, then open the answer.
What is the difference between deploy and release?
Deploy runs the new pods; release sends users to them. Progressive delivery separates the two.
When does blue-green fit better than canary?
When you want one clean switch and a fast way back, and can afford a full second copy for a while.
Who owns the release steps of checkout?
The product team, in checkout-config. The platform team owns the controller and the shared checks.
Where module 00 leaves you: Nothing new is installed. Your three repos and the cluster are as the Argo CD course left them, every Application is Synced and Healthy, and the reference repo is cloned next to your repos.