Deployment Methods
Fleeting- Référence externe : https://medium.com/buildpiper/canary-vs-blue-green-deployment-which-one-should-you-choose-a7d86d2929f0
deployment methods
While Blue/green deployments are used to eliminate downtime, Canary deployments are used to test a new feature in a production environment with minimal risk.
canary deployment
canary deployment is a technique for rolling out new features or changes to a small subset of users or servers before releasing the update to the entire system
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
done by creating a new replica set with the updated version of the software while keeping the original replica set running
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
small percentage of traffic is then routed to the new replica set, while the majority of the traffic continues to be served by the original replica set.
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
If issues are detected during the canary deployment, it can be quickly rolled back to the original replica set
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
rolling deployment
rolling deployment is a strategy for updating and deploying new versions of software in a controlled and gradual manner
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
rolls out changes incrementally, reducing the risk of downtime and allowing for easy rollbacks in case of errors
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
creating a new replica set with the updated version of the software while gradually scaling down the old replica set
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
allows for the new version to be deployed while the old version is still running, ensuring that there is no interruption to service
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
blue-green deployed
Blue-Green Kubernetes deployment strategy is a technique for releasing new versions of an application to minimise downtime and risk
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p
running two identical environments, one serving as the active production environment (blue) and the other as a new release candidate (green). The new release candidate is thoroughly tested before being switched with the production environment, allowing for a smooth transition without any downtime or errors
— https://dev.to/pavanbelagatti/kubernetes-deployments-rolling-vs-canary-vs-blue-green-4k9p