Using GitOps for Kubernetes Reliability at Scale
summary
Claim: GitOps automates large-scale chaos testing by treating experiments as code and running them whenever an application change occurs. Implementation uses LitmusChaos with a git-backed config store (deploy keys write workflow metadata to a Git repo) and FluxCD/GitHub workflows to pull experiments. Demo shows an nginx deployment change triggering an event-triggered chaos workflow that runs a pod-delete experiment and writes results back to Chaos Center, enabling repeatable, auditable chaos at scale.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:31What Chaos Engineering Is
- 2:53Summary
- 4:13Why Is It More Important in the Era of Cloud Native Devops
- 6:22Chaos Engineering Is a Solution for Reliability
- 15:31How Do You Pull a Chaos Experiment on Top of an Application Change That Is Rolled
- 17:33Demos
- 19:37Deploy Keys to Github
- 22:14Workflow Scheduler
related talks
26mUsing GitOps to Increase System Resiliency with LitmusChaos
27mPutting Chaos Into Continuous Delivery to Increase App...
45mGitops: The Kubernetes way
40mHow GitOps Changes Everything in CI/CD
47mGitOps - Using Git as your source of truth for build, deploy and observability
23mGitOps: yea or nay?
26mBuild a GitOps-Powered Kubernetes Testing Machin...
07mIntroduction to GitOps
