Using GitOps for Both Infrastructure and Applications
summary
Claim: GitOps covers both Kubernetes applications and cloud infrastructure by treating infra as Kubernetes custom resources and reconciling them via the same controllers. Demonstrated using Argo CD + Crossplane to create an RDS instance and an S3 bucket from Git and both appear in AWS immediately the sync completes. Contrasted with Terraform state issues where state is mutable and drift can go unnoticed, citing large production outages as the risk. The demo succeeds and shows unified workflows for apps and infra.
AI-written summary · about
chapters (9)
- 0:00Introduction to GitOps
- 1:00GitOps for applications
- 2:13Limitations of infrastructure
- 4:07Evaluating Terraform
- 6:31State management challenges
- 8:36Extending GitOps to infra
- 10:35Integrating Crossplane
- 12:47Demo of infrastructure tasks
- 15:13Scaling GitOps everywhere
related talks
16mWant to extend GitOps to Infrastructure and Workloads? Here's how.
30mGitOpsifying Cloud Infra with Crossplane, ArgoCD
07mIntroduction to GitOps
31mLeveraging GitOps to wrangle your clusters and projects
45mGitops: The Kubernetes way
35mGitOps - the holy grail of devops
02h 02mAn end-to-end GitOps Architecture: Terraform, Ansible, Kubernetes and AWS
06mKeynote: The Future of GitOps