Leveraging GitOps to wrangle your clusters and projects
summary
Demonstrates a concrete GitOps workflow using Argo CD installed with two kubectl commands, showing a live install on OpenShift, creating an app that auto-syncs and self-heal sync across clusters. Explains the pull-based agent model that polls Git, supports air‑gapped caches, and lets configuration changes (example: changing a console link from Google to Bing) propagate automatically. Mentions Flux and Jenkins X as alternatives, shows a small Flask app deployment in the repo, and confirms the changes actually apply and revert out‑of‑sync states.
AI-written summary · about
chapters (12)
- 0:00GitOps introduction
- 3:56CI/CD and GitOps basics
- 7:47GitOps for multiple clusters
- 10:55Git workflow for GitOps
- 12:21Push vs pull in GitOps
- 15:47GitOps tools and Argo CD
- 17:09Install Argo CD on OpenShift
- 18:37Manage clusters with Argo CD
- 22:28Configure cluster links via GitOps
- 25:18Syncing and self-healing with Argo CD
- 27:45Deploy app with GitOps
- 28:28Conclusion and future
related talks
36mKEYNOTE: Taking a step back and leveraging GitOps to wrangle your clusters and projects
30mManage your kubernetes cluster in the GITOPS way !!
29mDemystifying Gitops with ArgoCD
01h 19mTutorial: Everything You Need To Become a GitOps Ninja
27mImplementing GitOps with ArgoCD: A Practical Guide
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
30mGitOps: Keeping It Light, Bright, and Deployed Right with OpenShift!
26mGitOps: yea or nay?