CI/CD with GitOps and AKS
summary
Describes a GitOps CI/CD architecture on Azure Kubernetes Service where GitHub Actions build container images on commit, push them to a registry, update Kubernetes manifests, and a GitOps operator applies them. Compares Argo CD (web UI, automatic sync, rollbacks, RBAC) with Flux + Flagger (progressive rollouts, hub‑and‑spoke or standalone installs, supports Kustomize/Helm/YAML) and reports faster rollbacks and full environment reprovisioning in about 20–25 minutes.
AI-written summary · about
chapters (11)
- 0:00CI/CD with GitOps
- 2:12Push vs Pull in CI/CD
- 4:42What is AKS
- 8:46GitOps with AKS
- 10:10Flux CD in AKS
- 13:21Argo CD advantages
- 15:27GitOps use cases
- 18:59Legacy components
- 20:06CI vs CD
- 21:53Approval flows
- 24:25Summary
related talks
31mGitOps and Kubernetes: a Winning Combo
43mK8s Automation with Azure DevOps: A GitOps Approach w/o Tools
56mNavigating the GitOps ecosystem: The principles and in-depth look at Argo and Flux
37mDevelopers Love GitOps
22mPush to Prod: GitOps Workflows on k8s with FluxCD
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
31mLeveraging GitOps to wrangle your clusters and projects
38mGitOps x Kubernetes: Argo CD gives us the winning combo