Hands-On Microservices with Kubernetes

Blue-green deployment

Blue-green deployment is a well-known pattern. The idea is that you don't update the existing deployment; instead, you create a brand new deployment with the new version. Initially, your new version doesn't service traffic. Then, when you verify that the new deployment is up and running (you can even run some smoke tests against it), you switch all the traffic in one fell swoop from the current version to the new version. If you encounter any problems after you switch to the new version, you can instantly switch all the traffic back to the previous deployment, which is still up and running. When you are confident that the new deployment is doing well, you can destroy the previous deployment.

One of the greatest advantages ...