Which Deployment Strategy Should We Choose?
Explore the criteria for selecting deployment strategies in Kubernetes environments. Understand the use cases for recreate, rolling update, canary, and serverless deployments, and learn how to balance operational costs with deployment safety to make informed decisions tailored to your application's needs and cluster capabilities.
We saw some of the deployment strategies. There are others, and this chapter does not exclude you from exploring them. Please do that. The more you learn, the more educated decisions you’ll make. Still, until you figure out all the other strategies and variations you can do, we accumulated enough material to summarize what we learned so far.
Can we conclude that canary deployments are the best and that everyone should use them for all their applications? Certainly not. To begin with, if an application is not eligible for rolling updates (e.g., a single replica app), it is almost certainly not suitable for canary deployments. If we think of canaries as extensions of rolling updates, if an app is not a good candidate for the latter, it will also not be fit for the former.
Use case for Recreate strategy
In other words, there is a good use case for using the Recreate strategy in some cases, specifically for those applications that cannot (or shouldn’t) use one of the other strategies.
So, if both Canary and Recreate ...