Source: medium.com
Continuous Kubernetes blue-green deployments on Azure using Nginx, AppGatewCategory: Kubernetes, nginx
This is part two of my series on advanced deployment practices. Here now enters the practice of blue/green deployments which means that instead of replacing the previous version (here we refer to this version as blue), we bring up the new version (here referred to as the green version) next to the existing version, but not expose it to the actual users right away.
We will start with the Nginx deployment, which will leverage a single azure load balancer in front of our Nginx ingress controller in the AKS cluster.
Only if that is the case we will allow the deployment to progress and end up in the on successstep — if not we will execute the on failurestep to clean up the canary and delete the helm deployment in the green slot.
he next type of deployment will leverage the azure application gateway as ingress controller to achieve the same.
We will start with the Nginx deployment, which will leverage a single azure load balancer in front of our Nginx ingress controller in the AKS cluster.
Only if that is the case we will allow the deployment to progress and end up in the on successstep — if not we will execute the on failurestep to clean up the canary and delete the helm deployment in the green slot.
he next type of deployment will leverage the azure application gateway as ingress controller to achieve the same.
Related Articles
Community Partners
DevOps Careers