Managing infrastructure with Git: First principles of GitOps
summary
Argues that Git must be the single source of truth and shows concrete tooling and workflows: use CloudFormation drift detection (demo changes DynamoDB read capacity from 5 to 6 and drift is found), synthesize CDK into CloudFormation, run CFN‑Lint and cfn‑nag plus TaskCat in CI, gate with change sets, and deploy via a release branch merged from PRs (main = live). Offers a runnable solution for alerts: a Stack Drift Notifier Lambda that scans stacks and sends SNS/email or Slack when drift appears.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:45DevOps
- 4:11Infrastructure as Code
- 8:54Why use Git
- 13:09Happy Path
- 14:34Branching
- 16:16Drift detection
- 22:46CICD system
- 24:48CICD pipeline
- 26:09Pull Request
- 26:29Integration Testing
- 26:54Tools
- 28:12AWS ECS Continuous Deployment
- 28:37Resources
related talks
55mGitOps, Fostering Next-Generation Operations Teams
29mPutting the Ops in GitOps - New Challenges in Managing Cloud Native Environments
29mThe Evolution of GitOps in Platform Engineering
31mPanel Discussion: GitOps & Best Practices for Cloud Native CI/CD
19mGitOps 101: Demystifying GitOps
47mGitOps - Using Git as your source of truth for build, deploy and observability
16mWant to extend GitOps to Infrastructure and Workloads? Here's how.
30mDeclarative by Default, Secure by Design: GitOps as a Control Plane for Governance