Continuous Delivery On Kubernetes With GitOps
summary
Defines three concrete GitOps flavors: true GitOps — pull-only CD with an in-cluster operator (examples: Argo CD and Flux) that reduces external cluster access and enforces declarative repos; GitLab-flavored GitOps — CI/CD-centric mix of push and pull using the GitLab Kubernetes Agent with a two-phase agent model; and “hobo” GitOps — makeshift pull-like CD built with Jenkins or scripts. Claims Argo CD is the cleanest for Kubernetes, Google Application Delivery behaves similarly though it starts push-based.
AI-written summary · about
chapters (9)
- 0:00Introduction to GitOps
- 1:07What is GitOps definition
- 4:59True GitOps explained
- 15:42Adopting GitOps patterns
- 16:26Argo CD deep dive
- 21:17Security in GitOps
- 23:43Hobo GitOps flexibility
- 27:21Google's Application Delivery
- 30:05Q&A and closing
related talks
38mGitOps x Kubernetes: Argo CD gives us the winning combo
45mGitops: The Kubernetes way
06mGitOps - At a Glance
07mIntroduction to GitOps
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
34mImplementing GitOps on Kubernetes: ArgoCD
31mGitOps and Kubernetes: a Winning Combo
26mGitOps Lifecycle Management