From the course: Automating Kubernetes with GitOps

Unlock this course with a free trial

Join today to access over 24,900 courses taught by industry experts.

Using canary deployments

Using canary deployments - Kubernetes Tutorial

From the course: Automating Kubernetes with GitOps

Start my 1-month free trial Buy for my team

Using canary deployments

“

- Now that you know how to do blue-green, let's do canary deployments. A canary deployment upgrade strategy will expose a new-version of the application to a limited number of users before completing the migration to the new version. This allows user exposure with a minimized risk, and if things don't work out well, it's easy to revert to the previous situation by just removing the new application instance or instances. When you are going to create canary deployments, there's two ways that you can do it. You can base them on services or on ingress. Using ingress is preferred as the application picks up the change without reconnecting, and service-based canary deployments are configured to use a common selector label on the old as well as the new applications. Ingress-based canary deployments are using two ingress resources pointing to the same ingress virtual host. Now that you know how canary deployments are organized,…

Contents