Why need Canary Deployment
What Is Canary Deployment
Canary deployments are a staged release practice. We roll out software updates to a small group of users first so they can test them and provide feedback. Once the changes are accepted, the update will be rolled out to the remaining users.
Itis often combined with Rolling Deployment to create an approach that Brings together the best of both worlds.
Canary deployments are a method of staged release [1]. To test the upgrades and get user input, we release them to a select sample of users first. The remaining users will receive the update after the modifications are approved. Canary deployments might be accomplished extremely well with mesh service (istio).
The most well-known open source service mesh software is called Istio. Service-to-service communication is handled by a separate infrastructure layer called a service mesh. It is in charge of ensuring that requests are delivered reliably through the intricate web of services that makes up a contemporary, cloud-native application. In actual use, the service mesh is usually implemented as a collection of thin network proxies that are installed concurrently with application code without the requirement for the application to be aware of it.
Reference List
- Canary Deployment strategy for Kubernetes (n.d.). Retrieved November 26, 2022, from https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/kubernetes/canary-demo?view=azure-devops&tabs=yaml