GitOps: From Commit to Deploy
summary
CI uses GitHub Actions builds and pushes Docker images (build step captures a version output, logs into DockerHub with a token, then checks out a separate configuration repo). Kustomize overlays are edited (sed replaces the image tag) and committed to the config repo, then ArgoCD syncs kustomize overlays to clusters (project maps repos to staging/prod, TLS required). Deploy strategies include blue/green and canary rollout increments a single canary pod for baseline vs canary observation before rolling traffic over.
AI-written summary · about
chapters (16)
- 0:00Introduction to GitOps
- 1:03What is GitOps?
- 4:17Separate repositories for apps and config
- 7:05Continuous integration basics
- 16:18GitOps with CI and config updates
- 25:39Continuous delivery vs deployment
- 26:43Argo CD overview and features
- 29:10Installing and setting up Argo CD
- 35:38Using Argo CD CLI and UI
- 38:14Creating Argo CD applications
- 41:04Syncing and managing deployments
- 45:38Customize vs Helm for GitOps
- 47:49Rollbacks and reverting changes
- 50:22Argo CD extensions: Workflows and Events
- 52:29Blue-green and canary deployments
- 56:03Summary and Q&A
related talks
20mMulti-Stage Deployment Pipelines the GitOps Way
37mGitHub Actions + K8S to level up software dev
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
31mGitOps and Kubernetes: a Winning Combo
29mGitOps on all layers – maintain your Kubernetes cluster! — Hafid Haddouti
16mUse Kubernetes-native Integrated GitOps CI/CD Workflows
30mGitOps: Keeping It Light, Bright, and Deployed Right with OpenShift!
18mGitOps powered CICD-Glueing it together with Argo Workflows, Events