GitOps Canary Deployments to Kubernetes with Istio, Argo CD and Flagger

Deploying a new version of a software application is the bread and butter of the development lifecycle. However, you still have to think through and strategize around how you're going to get this newly deployed version into the hands of your end users or whatever clients will be consuming it. In this video, I'll discuss how you can make use GitOps with a canary strategy to release newly deployed software in an automated and controlled way.
We probably all wish releasing a new software version was as easy as just putting it out there and moving on. Unfortunately, it's not that simple.
How do we know our most recent changes work as they should? Can we use some mechanism to release it to a subset of clients to get an idea of the success and failure of this new implementation? Can we roll back in case things aren't working out as they should? And can this whole process be automated? That's what this video will focus on.
#kubernetes #istio #servicemesh #argocd #gitops
Timestamps:
00:00 - Introduction
00:14 - Managing application releases for newly deployed software
01:12 - Canary release strategy
02:21 - Architecture overview of a solution consisting of Argo CD, Istio, and Flagger for GitOps canary release
03:30 - Walk-through of application source, live stable version of the application, GitHub Actions configuration, Argo CD application, Flagger canary resource, and Istio gateway configuration
11:28 - Demonstration of releasing new application version
Repositories with source code:
github.com/LukeMwila/istio-ga...
github.com/LukeMwila/microser...
github.com/LukeMwila/microser...
Other relevant videos:
Using Istio Gateway to Route Traffic to Microservices on Amazon EKS - • Using Istio Gateway to...
Getting Started with ArgoCD for GitOps Deployments - • Getting Started with A...
Using Argo CD & Datree for Stable Kubernetes CI/CD Deployments - • Using Argo CD & Datree...
Connect:
GitHub: github.com/LukeMwila
Twitter: / luke9ine
Medium: / outlier.developer
LinkedIn: / lukonde-m. .
If you found this video helpful, please like the video and subscribe to the channel!

[@sg8168]

ArgoCD will self-heal the changes by flagger, how to handle this?

[@LukondeMwila]

Hey @sg8168, sorry for the very late response. You can configure the sync interval in ArgoCD using the timeout.reconciliation value in the argocd-cm ConfigMap. Also, the canary rollout duration by Flagger is something you can configure. So you just need to make sure they don't conflict. For example, Flaggers canary rollout time should be less than the ArgoCD sync interval. This way Flagger has enough time to either rollout or rollback before ArgoCD tries to self-heal.

[@softwareengineer5764]

Nobody can compete you Lukonde on youtube👏👏👏👏👏. Such an amazing and high quality content out there. No words 😶