Using GitOps to Increase System Resiliency with LitmusChaos
summary
LitmusChaos installs on Kubernetes and is wired to a Git repo so workflows become a single source of truth and auto-sync both ways; demo shows a pod-delete experiment on a bank app that runs, the service terminates then recovers, and workflow YAMLs appear in Git. GitOps triggers via branch, PR and merge launch experiments (example: chaos duration 60→100s and interval 30→50s updated from Git). Features shown: bi-directional Git sync, Prometheus observability, RBAC and multi‑tenant workflow scheduling.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:10What is Resilience?
- 2:16Adopt Chass Engineering
- 3:09Foundations of Cloud-Native Chaor Engineering
- 5:46Chaos Center
- 6:46Workflow Management
- 7:17Multi Tenancy
- 8:33Non Kubernetes Chaos
related talks
30mUsing GitOps for Kubernetes Reliability at Scale
27mPutting Chaos Into Continuous Delivery to Increase App...
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
32mChaos Engineering with Litmus and Jenkins
28mChaos Engineering alongside Litmus and Jenkins
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
34mChaos Engineering For Hybrid Targets With LitmusChaos
30mFrom Chaos to Quality: Elevating LitmusChaos with CI/CD and Pull R...