**The First Half of 2026 with LitmusChaos: Scaling Resilience Testing at the CNCF**
Authored by Pritesh Kiri
—
The first half of 2026 was one of the busiest stretches for the **LitmusChaos** project. Under the stewardship of the Cloud Native Computing Foundation (CNCF), the open-source chaos engineering platform saw significant community growth, major enterprise adoption, and critical software releases.
As organizations increasingly rely on cloud-native infrastructure, the need for proactive resilience testing has never been greater. LitmusChaos provides the tooling necessary to identify weaknesses and prevent potential outages by running controlled experiments in Kubernetes and beyond.
This article details the project’s progress in the first half of 2026, covering community growth, release notes, partnerships, and real-world applications.
—
## Community Growth Highlights (January – June 2026)
The following metrics demonstrate LitmusChaos’s expanding influence across the cloud-native landscape:
* **LinkedIn Following:** Increased by **+39%** (from 769 to 1,069), driven by in-person events, KubeCon India, and community meetups rather than passive online content.
* **Contributor Base:** Grew by **+16%** (from 241 to 279), indicating sustained and healthy community development across six releases.
* **GitHub Stars:** Rose by **+7.4%** (from 5,118 to 5,496), a steady climb that suggests long-term project health.
—
## Project Releases: 3.25.0 – 3.30.0
LitmusChaos maintained a consistent release cadence, shipping a new version every month. Each release focused on stability, security, and user experience.
### Release 3.30.0 (June 2026)
*Infrastructure hardening and security.*
* **Highlights:** New metrics port for `litmusportal-server`, GraphQL config fixes, and tighter RBAC (Role-Based Access Control) on project membership queries.
* **Security:** Patches to Docker base images and Go dependencies.
### Release 3.29.0 (May 2026)
*Observability and stability.*
* **Highlights:** Patched CVE-2026-33186 via gRPC version bump. Introduced Prometheus metrics support with a getting-started guide.
* **Bug Fixes:** Resolved a bug allowing duplicate chaos experiment triggers under concurrent reconciles.
### Release 3.28.0 (April 2026)
*Enterprise adoption and hardening.*
* **Highlights:** Official adoption by **Canonical** (the company behind Ubuntu). Fixed a stale config leak across probes and a subscriber crash on Workflow ADD events.
* **Security:** Upgraded the frontend base image to UBI9 to resolve a Python vulnerability.
### Release 3.27.0 (March 2026)
*Feature expansion and reliability.*
* **Highlights:** Introduced support for targeting **Kubernetes Jobs** in chaos experiments.
* **Reliability:** Fixed a subscriber crash caused by a nil pointer dereference and removed a 1024-character limit on CMD probe commands.
### Release 3.26.0 (February 2026)
*Maintenance and CI health.*
* **Highlights:** Focused on Continuous Integration (CI) fixes, updated contributor documentation, and cleanup of the frontend build pipeline.
### Release 3.25.0 (January 2026)
*Reliability and tooling.*
* **Highlights:** Fixed a persistent blank-screen bug on ChaosCenter portal refresh. Added a Docker linter to CI and a GitHub Action for release artifact generation.
—
## Case Study: Flipkart – Winning the CNCF Contest
The most significant milestone of the period occurred at **KubeCon + CloudNativeCon India 2026**.
* **The Win:** Flipkart won the CNCF End User Case Study Contest for their journey in building a multi-tenant chaos platform on LitmusChaos.
* **The Challenge:** Flipkart runs hundreds of tightly coupled microservices that must withstand the traffic of “Big Billion Days” and festive sales.
* **The Solution:** To move resilience from an afterthought to a practice, Flipkart built a centralized chaos platform featuring:
* A hybrid multi-tenancy architecture between cluster-wide and namespace-wide installs.
* A DaemonSet-based high-availability model for chaos injection.
* A Script Runner for dynamic target selection.
* A hybrid VM chaos extension for non-Kubernetes workloads.
* **Contribution:** Flipkart contributed five fixes back to the LitmusChaos upstream project, including database index fixes and duplicate-name validation repairs.
—
## Project Pavilion at KubeCon India
The LitmusChaos booth saw between 100 and 200 visitors daily. Key topics of interest included:
* The distinction between **Resilience Testing** and traditional testing in the age of AI.
* **ChaosHub** as the default, out-of-the-box fault library covering Kubernetes, Linux, AWS, and GCP.
* **Automating Chaos** in CI/CD pipelines using LitmusCTL and Terraform.
* The introduction of the **LitmusChaos MCP (Model Context Protocol)**, allowing engineers to interact with chaos engineering via natural language.
—
## Community Events
The project remained active globally through in-person meetups:
* **Bangalore:** Three Resilience Testing meetups were hosted in collaboration with the Cloud Computing Circle.
* **Online:** Monthly community and contributor meetings were held regularly, with recordings available on the project’s YouTube channel.
* **Travel:** The project spoke at DevConf India, FOSSASIA in Bangkok, and Open Source Days in Ahmedabad.
—
## Frequently Asked Questions (FAQ)
**Q1: What is LitmusChaos?**
LitmusChaos is an open-source chaos engineering platform designed for Kubernetes. It helps teams identify weaknesses in their infrastructure by running controlled, experimental chaos events to validate system resilience.
**Q2: How can I get involved with LitmusChaos?**
You can join the `#litmus` channel on Kubernetes Slack, attend the monthly community meetings, or review the Contributing Guide available on the project’s website. Contributions are welcome from both end-users and vendors.
**Q3: Is LitmusChaos production-ready?**
Yes. The project has seen significant adoption by enterprises like Flipkart and Canonical. The consistent release schedule (six releases in six months) and focus on infrastructure hardening demonstrate its readiness for production use.
**Q4: What is ChaosHub?**
ChaosHub is the official curated library of faults and experiments for LitmusChaos. It provides pre-built chaos experiments for Kubernetes, Linux, and various cloud providers (AWS, GCP, Azure), making it the “default fault library” for users.
**Q5: What is the LitrusChaos MCP?**
The Model Context Protocol (MCP) integration allows engineers to interact with and learn about chaos engineering through natural language, lowering the barrier to entry for the practice.
—
## Conclusion
The first half of 2026 was a period of intense growth and validation for LitmusChaos. With six major releases, a 39% increase in social community engagement, and the prestigious win at the CNCF Contest by Flipkart, the project has solidified its role as a leader in the cloud-native resilience space.
Moving into the second half of the year, the project aims to build on this momentum with more production adopters, further upstream contributions, and expanded in-person community interactions. LitmusChaos continues to empower teams to “Keep Learning. Keep Testing. Keep Building Resilience.”
