Flipkart's Chaos Engineering Revolution: Insights from KubeCon + CloudNativeCon India 2026
In today's fast-paced digital landscape, system resilience is paramount. Chaos engineering addresses this by intentionally introducing faults to uncover weaknesses in your infrastructure. Flipkart's Central Reliability Engineering team has taken this discipline to the next level by building a centralized chaos platform on top of LitmusChaos, an open-source chaos engineering platform designed to help teams identify vulnerabilities in their systems.
The implementation at Flipkart includes several key customizations. They developed a hybrid multi-tenancy architecture to support various teams and workloads. A DaemonSet-based high-availability model for chaos injection ensures that faults can be introduced consistently across the cluster. Additionally, they created a Script Runner fault that allows for dynamic target selection and context chaining, enhancing the flexibility of their chaos experiments. For non-Kubernetes workloads, they also integrated a hybrid VM chaos extension, ensuring that their chaos engineering practices extend beyond just containerized environments.
In production, it's crucial to understand the implications of chaos engineering. While the benefits are significant, introducing faults can lead to unexpected behavior if not managed carefully. Ensure that your team is prepared for the potential fallout and has robust monitoring in place to observe the effects of injected chaos. The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Key takeaways
- →Implement a hybrid multi-tenancy architecture for chaos engineering to support diverse workloads.
- →Utilize a DaemonSet-based model for high-availability chaos injection across your Kubernetes cluster.
- →Leverage Script Runner faults for dynamic target selection and context chaining in your chaos experiments.
- →Extend chaos engineering practices to non-Kubernetes workloads with a hybrid VM chaos extension.
Why it matters
By adopting chaos engineering, teams can proactively identify and address weaknesses, leading to more resilient systems and improved user experiences. This approach minimizes downtime and enhances overall service reliability.
When NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsIndustry-standard certifications built by the people behind Linux and Kubernetes. Earn the CKA — the gold standard Kubernetes administrator cert. OpsCanary readers get 30% off year-round with code OPSCANARY3.
Get CKA certified →Kubernetes v1.37: Metrics API Stabilization and Its Impact
Kubernetes v1.37 has promoted the metrics.k8s.io API to stable, a crucial step for monitoring resource usage in your clusters. This API provides real-time CPU and memory metrics for nodes and Pods, enabling effective autoscaling and performance tuning.
The Lazy Developer’s Guide to Observing Your Code with OpenTelemetry
Observability is crucial for maintaining healthy applications, yet many developers shy away from it. With zero-code instrumentation, you can add observability without touching your source code. This guide will show you how to leverage OpenTelemetry effectively.
Automating RCA at Scale: Mastering Multi-Signal Correlation in Kubernetes
Root Cause Analysis (RCA) can be a nightmare in cloud-native environments. Multi-signal correlation offers a structured approach to pinpoint issues by analyzing anomalies across various signals. This article dives into how this method works and what you need to implement it effectively.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.