News
What happened
KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away... KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away with a keynote slot, a packed project booth, and conversations that will shape how we think about growing this community in India and beyond. Flipkart and LitmusChaos: The CNCF End User Case Study contest and keynote The highlight of the event for us came before a single session even started. Flipkart was selected as the winner of the CNCF End User Case Study Contest India, with a story that featured LitmustChaos. This honor earned us a keynote slot alongside Flipkart on the main stage at KubeCon India 2026. This recognition is a reflection of the real-world impact LitmusChaos is having at scale. It is not just about the project itself. It is about the organizations that have adopted it, built on top of it, and contributed their learnings back to the community. Flipkart’s story is exactly that. Keynote: From afterthought to practice From Afterthought to Practice: How Flipkart Built a Multi-tenant Chaos Platform on LitmusChaos Aditya Sridasyam, Software Development Engineer, Flipkart, and Uma Mukkara, Head of Resilience Testing Flipkart runs hundreds of tightly coupled microservices that need to hold up under the kind of traffic that Big Billion Days and festive sales generate. For a long time, resilience was something the team dealt with after an outage, not before. To change that, Flipkart’s Central Reliability Engineering team built a centralized chaos platform on top of LitmusChaos. What made this talk stand out was the specificity. Aditya walked through four concrete customizations Flipkart made to run LitmusChaos at thei
KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away... KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away with a keynote slot, a packed project booth, and conversations that will shape how we think about growing this community in India and beyond. Flipkart and LitmusChaos: The CNCF End User Case Study contest and keynote The highlight of the event for us came before a single session even started. Flipkart was selected as the winner of the CNCF End User Case Study Contest India, with a story that featured LitmustChaos. This honor earned us a keynote slot alongside Flipkart on the main stage at KubeCon India 2026. This recognition is a reflection of the real-world impact LitmusChaos is having at scale. It is not just about the project itself. It is about the organizations that have adopted it, built on top of it, and contributed their learnings back to the community. Flipkart’s story is exactly that. Keynote: From afterthought to practice From Afterthought to Practice: How Flipkart Built a Multi-tenant Chaos Platform on LitmusChaos Aditya Sridasyam, Software Development Engineer, Flipkart, and Uma Mukkara, Head of Resilience Testing Flipkart runs hundreds of tightly coupled microservices that need to hold up under the kind of traffic that Big Billion Days and festive sales generate. For a long time, resilience was something the team dealt with after an outage, not before. To change that, Flipkart’s Central Reliability Engineering team built a centralized chaos platform on top of LitmusChaos. What made this talk stand out was the specificity. Aditya walked through four concrete customizations Flipkart made to run LitmusChaos at their scale: a hybrid multi-tenancy architecture that sits between cluster-wide and namespace-wide installs, a DaemonSet-based high-availability model for chaos injection, a Script Runner fault that enables dynamic target selection and context chaining, and a hybrid VM chaos extension for workloads that are not running on Kubernetes. These are the kinds of production-hardened decisions that come from running chaos engineering at the scale Flipkart operates at. Uma Mukkara provided context on how contributions like these flow back upstream and benefit the broader LitmusChaos community. For a full look at Flipkart’s reference architecture, platform design, and the measurable impact numbers, read the CNCF Flipkart case study . Project pavilion conversations Our project booth at the pavilion saw between a hundred and two hundred visitors. The conversations ranged from first-time introductions to chaos engineering to deep technical discussions on architecture and integrations. Below is a summary of what came up most at the booth. Resilience Testing and Reliability in the Age of AI: AI inference workloads are fragile in ways traditional services are not, and a lot of the conversations at the booth were about how chaos engineering fits into that new reality. ChaosHub: The Default Fault Library: We walked many people through ChaosHub, LitmusChaos’s ready-to-use fault library covering Kubernetes, Linux, AWS, GCP, and more. For most, it was the first time they realized how much is available out of the box. Automating Chaos in CI/CD: A common ask was how to shift chaos left. We covered integrating LitmusChaos into pipelines using LitmusCTL, the SDKs, and Terraform without requiring teams to overhaul their existing delivery process. Tool Comparisons and Ecosystem Positioning: We had several side-by-side comparisons with other chaos engineering tools, focusing on where LitmusChaos fits and why the CNCF-backed, community-driven model matters for long-term adoption. Custom Chaos and Best Practices: For teams with infrastructure patterns not covered by the default library, we discussed how to build custom experiments and what a mature chaos engineering practice looks like at different stages. LitmusChaos MCP: We introduced the LitmusChaos MCP, a Model Context Protocol integration that lets engineers interact with and learn chaos engineering through natural language, lowering the barrier to entry for teams just getting started. New Adopters: We shared that Canonical and Intertech have recently joined as official adopters. Flipkart’s story on the keynote stage the same day added strong validation of the project’s production-readiness to that conversation. Alongside the technical conversations, we ran a Chaos Bird game at the booth, a leaderboard-based take on Flappy Bird where the top scorers won LitmusChaos swag. We also ran a separate random giveaway throughout both days. The engagement was high, and the leaderboard kept people coming back. A word on what this event meant The KubeCon + CloudNativeCon India audience is largely practitioners building and running systems in India, working with constraints and at scale. The interest in LitmusChaos here was genuine and grounded. The questions were specific. That is exactly the kind of community engagement that makes a project better. Sharing Flipkart’s story for the winning CNCF End User Case Study Contest is a milestone for the project and for the Indian cloud native community. We are grateful to Aditya and the Flipkart team for sharing their work and to Uma for anchoring the session. We are also grateful to CNCF and the event organizers for creating the space for this kind of recognition. Stay connected with LitmusChaos If KubeCon + CloudNativeCon India was your first introduction to LitmusChaos, here are some ways to go deeper: Visit the LitmusChaos website for architecture, use cases, and getting-started guides. Join the #litmus channel on Kubernetes Slack to ask ques
PRIVACY STACK
Extend Privacy Beyond DNS
Controlling your DNS queries is one layer of network privacy. Your email metadata — who you talk to, when, how often — is equally exposed with standard providers. Proton Mail applies end-to-end encryption to the layer most people ignore.
Try Proton Mail →This is an affiliate link. If you purchase, I earn a commission at no extra cost to you.
Changes at a glance
What's new
KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away... KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away with a keynote slot, a packed project booth, and conversations that will shape how we think about growing this community in India and beyond. Flipkart and LitmusChaos: The CNCF End User Case Study contest and keynote The highlight of the event for us came before a single session even started. Flipkart was selected as the winner of the CNCF End User Case Study Contest India, with a story that featured LitmustChaos. This honor earned us a keynote slot alongside Flipkart on the main stage at KubeCon India 2026. This recognition is a reflection of the real-world impact LitmusChaos is having at scale. It is not just about the project itself. It is about the organizations that have adopted it, built on top of it, and contributed their learnings back to the community. Flipkart’s story is exactly that. Keynote: From afterthought to practice From Afterthought to Practice: How Flipkart Built a Multi-tenant Chaos Platform on LitmusChaos Aditya Sridasyam, Software Development Engineer, Flipkart, and Uma Mukkara, Head of Resilience Testing Flipkart runs hundreds of tightly coupled microservices that need to hold up under the kind of traffic that Big Billion Days and festive sales generate. For a long time, resilience was something the team dealt with after an outage, not before. To change that, Flipkart’s Central Reliability Engineering team built a centralized chaos platform on top of LitmusChaos. What made this talk stand out was the specificity. Aditya walked through four concrete customizations Flipkart made to run LitmusChaos at their scale: a hybrid multi-tenancy architecture that sits between cluster-wide and namespace-wide installs, a DaemonSet-based high-availability model for chaos injection, a Script Runner fault that enables dynamic target selection and context chaining, and a hybrid VM chaos extension for workloads that are not running on Kubernetes. These are the kinds of production-hardened decisions that come from running chaos engineering at the scale Flipkart operates at. Uma Mukkara provided context on how contributions like these flow back upstream and benefit the broader LitmusChaos community. For a full look at Flipkart’s reference architecture, platform design, and the measurable impact numbers, read the CNCF Flipkart case study . Project pavilion conversations Our project booth at the pavilion saw between a hundred and two hundred visitors. The conversations ranged from first-time introductions to chaos engineering to deep technical discussions on architecture and integrations. Below is a summary of what came up most at the booth. Resilience Testing and Reliability in the Age of AI: AI inference workloads are fragile in ways traditional services are not, and a lot of the conversations at the booth were about how chaos engineering fits into that new reality. ChaosHub: The Default Fault Library: We walked many people through ChaosHub, LitmusChaos’s ready-to-use fault library covering Kubernetes, Linux, AWS, GCP, and more. For most, it was the first time they realized how much is available out of the box. Automating Chaos in CI/CD: A common ask was how to shift chaos left. We covered integrating LitmusChaos into pipelines using LitmusCTL, the SDKs, and Terraform without requiring teams to overhaul their existing delivery process. Tool Comparisons and Ecosystem Positioning: We had several side-by-side comparisons with other chaos engineering tools, focusing on where LitmusChaos fits and why the CNCF-backed, community-driven model matters for long-term adoption. Custom Chaos and Best Practices: For teams with infrastructure patterns not covered by the default library, we discussed how to build custom experiments and what a mature chaos engineering practice looks like at different stages. LitmusChaos MCP: We introduced the LitmusChaos MCP, a Model Context Protocol integration that lets engineers interact with and learn chaos engineering through natural language, lowering the barrier to entry for teams just getting started. New Adopters: We shared that Canonical and Intertech have recently joined as official adopters. Flipkart’s story on the keynote stage the same day added strong validation of the project’s production-readiness to that conversation. Alongside the technical conversations, we ran a Chaos Bird game at the booth, a leaderboard-based take on Flappy Bird where the top scorers won LitmusChaos swag. We also ran a separate random giveaway throughout both days. The engagement was high, and the leaderboard kept people coming back. A word on what this event meant The KubeCon + CloudNativeCon India audience is largely practitioners building and running systems in India, working with constraints and at scale. The interest in LitmusChaos here was genuine and grounded. The questions were specific. That is exactly the kind of community engagement that makes a project better. Sharing Flipkart’s story for the winning CNCF End User Case Study Contest is a milestone for the project and for the Indian cloud native community. We are grateful to Aditya and the Flipkart team for sharing their work and to Uma for anchoring the session. We are also grateful to CNCF and the event organizers for creating the space for this kind of recognition. Stay connected with LitmusChaos If KubeCon + CloudNativeCon India was your first introduction to LitmusChaos, here are some ways to go deeper: Visit the LitmusChaos website for architecture, use cases, and getting-started guides. Join the #litmus channel on Kubernetes Slack to ask ques
Breaking changes
No breaking changes were reported in the source material.
Analysis
In detail
KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away... KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away with a keynote slot, a packed project booth, and conversations that will shape how we think about growing this community in India and beyond. Flipkart and LitmusChaos: The CNCF End User Case Study contest and keynote The highlight of the event for us came before a single session even started. Flipkart was selected as the winner of the CNCF End User Case Study Contest India, with a story that featured LitmustChaos. This honor earned us a keynote slot alongside Flipkart on the main stage at KubeCon India 2026. This recognition is a reflection of the real-world impact LitmusChaos is having at scale. It is not just about the project itself. It is about the organizations that have adopted it, built on top of it, and contributed their learnings back to the community. Flipkart’s story is exactly that. Keynote: From afterthought to practice From Afterthought to Practice: How Flipkart Built a Multi-tenant Chaos Platform on LitmusChaos Aditya Sridasyam, Software Development Engineer, Flipkart, and Uma Mukkara, Head of Resilience Testing Flipkart runs hundreds of tightly coupled microservices that need to hold up under the kind of traffic that Big Billion Days and festive sales generate. For a long time, resilience was something the team dealt with after an outage, not before. To change that, Flipkart’s Central Reliability Engineering team built a centralized chaos platform on top of LitmusChaos. What made this talk stand out was the specificity. Aditya walked through four concrete customizations Flipkart made to run LitmusChaos at their scale: a hybrid multi-tenancy architecture that sits between cluster-wide and namespace-wide installs, a DaemonSet-based high-availability model for chaos injection, a Script Runner fault that enables dynamic target selection and context chaining, and a hybrid VM chaos extension for workloads that are not running on Kubernetes. These are the kinds of production-hardened decisions that come from running chaos engineering at the scale Flipkart operates at. Uma Mukkara provided context on how contributions like these flow back upstream and benefit the broader LitmusChaos community. For a full look at Flipkart’s reference architecture, platform design, and the measurable impact numbers, read the CNCF Flipkart case study . Project pavilion conversations Our project booth at the pavilion saw between a hundred and two hundred visitors. The conversations ranged from first-time introductions to chaos engineering to deep technical discussions on architecture and integrations. Below is a summary of what came up most at the booth. Resilience Testing and Reliability in the Age of AI: AI inference workloads are fragile in ways traditional services are not, and a lot of the conversations at the booth were about how chaos engineering fits into that new reality. ChaosHub: The Default Fault Library: We walked many people through ChaosHub, LitmusChaos’s ready-to-use fault library covering Kubernetes, Linux, AWS, GCP, and more. For most, it was the first time they realized how much is available out of the box. Automating Chaos in CI/CD: A common ask was how to shift chaos left. We covered integrating LitmusChaos into pipelines using LitmusCTL, the SDKs, and Terraform without requiring teams to overhaul their existing delivery process. Tool Comparisons and Ecosystem Positioning: We had several side-by-side comparisons with other chaos engineering tools, focusing on where LitmusChaos fits and why the CNCF-backed, community-driven model matters for long-term adoption. Custom Chaos and Best Practices: For teams with infrastructure patterns not covered by the default library, we discussed how to build custom experiments and what a mature chaos engineering practice looks like at different stages. LitmusChaos MCP: We introduced the LitmusChaos MCP, a Model Context Protocol integration that lets engineers interact with and learn chaos engineering through natural language, lowering the barrier to entry for teams just getting started. New Adopters: We shared that Canonical and Intertech have recently joined as official adopters. Flipkart’s story on the keynote stage the same day added strong validation of the project’s production-readiness to that conversation. Alongside the technical conversations, we ran a Chaos Bird game at the booth, a leaderboard-based take on Flappy Bird where the top scorers won LitmusChaos swag. We also ran a separate random giveaway throughout both days. The engagement was high, and the leaderboard kept people coming back. A word on what this event meant The KubeCon + CloudNativeCon India audience is largely practitioners building and running systems in India, working with constraints and at scale. The interest in LitmusChaos here was genuine and grounded. The questions were specific. That is exactly the kind of community engagement that makes a project better. Sharing Flipkart’s story for the winning CNCF End User Case Study Contest is a milestone for the project and for the Indian cloud native community. We are grateful to Aditya and the Flipkart team for sharing their work and to Uma for anchoring the session. We are also grateful to CNCF and the event organizers for creating the space for this kind of recognition. Stay connected with LitmusChaos If KubeCon + CloudNativeCon India was your first introduction to LitmusChaos, here are some ways to go deeper: Visit the LitmusChaos website for architecture, use cases, and getting-started guides. Join the #litmus channel on Kubernetes Slack to ask ques
Key takeaways
The most important facts from this update.
Why it matters
If you run self-hosted infrastructure, homelab services, or automation stacks, this update is worth tracking before you change production.
Homelab impact
If you run related services in your homelab, review whether this update affects your current deployment. Check compatibility with your Docker Compose files, reverse proxy config, or network setup before you upgrade production stacks.
What to do next
Practical steps for operators running self-hosted stacks.
This brief covers what you need from CNCF Blog's reporting. Visit the original post for release notes, changelogs, and full technical documentation.