All technological notes.
| strategy | Desc |
|---|---|
Recreate / big bang |
Stop all old Pods, then create all new Pods |
RollingUpdate /Ramped/ Incremental |
Gradually replace the old Pods with the new ones |
Canary / pilot / Grayscale Release |
Create a very small number of new Pods for testing, then replace all the remaining Pods. |
A/B testing |
Create a small number of new Pods to collect data |
Blue/Green |
Deploy new Pods in parallel with old pods. Swith when ready and delete the old one |
Shadowing / Traffic mirroring / Dark launch |
Deploy new Pods in parallel with old pods. return respone from only the old pods |
minReadySeconds + kubectl rollout pause
canary pod) and test the new podcanary pod acts as expected, kubectl rollout resume to resumecanary Deployment for the canary Pods with low replicasService forward traffic to canary DeploymentCanary deployment meets requirments, roll out the old deployment and delete Canary deployment
deployments and 2 servicesingress and path rule to route traffic forward to 2 services based on the condition
Blue Deployment: the stable production deploymentGreen Deployment: the deployment along with production deployment
Service with label selector targeting the Blue DeploymentGreen Deployment for testingGreen Deployment meets the requirements, update the Service’s label selector to target the Green Deployment
shdowing deployment with shadowing serviceingress
shdowing deploymentshdowing deployment