GitOps powered CICD-Glueing it together with Argo Workflows, Events
summary
GitOps CI/CD uses Argo Workflows, Argo Events and Argo CD to trigger containerized build steps on push, create a namespace and new ApplicationSet entry for feature branches, and delete that environment when the branch is removed. A sensor filters GitHub/GitLab webhooks, templates parameterize Maven/Gradle/JDK versions via a checked-in workflow descriptor, and the pipeline updates the deployment repo with the new image tag. Demo runs end to end and the delete workflow succeeds.
AI-written summary · about
chapters (11)
- 0:00GitOps powered CI/CD intro
- 1:06CI/CD pipeline objectives
- 2:32Trigger workflows with Argo Events
- 5:04Build apps with Argo Workflows
- 6:28Deploy with Argo CD
- 7:32End-to-end GitOps workflow
- 8:16Ephemeral feature environments
- 9:21Branch build configs
- 10:48Meta workflows
- 12:38Monitor and clean workflows
- 13:21Q&A
related talks
43mGitOps at Scale with and Argo CD on
27mImplementing GitOps with ArgoCD: A Practical Guide
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
57mGitOps: From Commit to Deploy
42mArgo Family: GitOps in first class
39mBuild and Deploy Your Application with Argo on Kubernetes
38mGitOps x Kubernetes: Argo CD gives us the winning combo
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes