GitOps and Kubernetes: a Winning Combo
summary
Claims GitOps makes Git the single source of truth and automates desired state for apps and infra, demonstrated by deploying a simple "hello k8s" repo with kustomize into Azure Kubernetes Service using Argo CD (auto-sync creates dev and prod namespaces). Mentions alternatives like Flux and Atlantis, explains pull-based operators vs push CI, recommends selecting an app, runtime, GitOps operator and sync method, and says the demo deploys successfully though UI can be slow.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:14About Steve
- 2:03Software Business
- 2:30Digital Acceleration
- 4:16Digital Business
- 5:21Every Business is a Software Business
- 6:36Question to ask yourself
- 7:18Every industry is being disrupted
- 9:14A journey and a story
- 10:16The current state of the company
- 11:43Cloud and Kubernetes
- 12:49CICD
- 13:19GitOps
- 14:22GitOps History
- 15:45Push Code Not Containers
- 16:39GitOps Principles
- 18:32Flux
- 19:52GitOps and Kubernetes
- 21:09Push vs Pull
- 22:08GitOps Workflow
- 23:31How to adopt GitOps
- 24:14Figure out your runtime environment
- 24:34Decide on tooling
- 25:29Demo
- 26:22Demo in Azure
related talks
23mGitOps: yea or nay?
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
45mGitops: The Kubernetes way
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
38mGitOps x Kubernetes: Argo CD gives us the winning combo
47mGitOps - Using Git as your source of truth for build, deploy and observability
25mCI/CD with GitOps and AKS
43mK8s Automation with Azure DevOps: A GitOps Approach w/o Tools