litmuschaos /litmus
Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
★ 5,746⑂ 906👁 80⑃ 3,811● 1,795▤ 122
-1
日增长
5,746
stars
906
forks
80
watchers
3,811
prs
1,795
issues
122
releases
README
LitmusChaos Open Source Chaos Engineering Platform !GitHub Workflow Read this in other languages. 🇰🇷 🇨🇳 🇧🇷 🇮🇳 🇪🇸 Overview LitmusChaos is an open source Chaos Engineering platform that enables teams to identify weaknesses & potential outages in infrastructures by inducing chaos tests in a controlled way. Developers & SREs can practice Chaos Engineering with LitmusChaos as it is easy to use, based on modern Chaos Engineering principles & community collaborated. It is 100% open source & a CNCF project. LitmusChaos takes a cloud-native approach to create, manage and monitor chaos. The platform itself runs as a set of microservices and uses Kubernetes custom resources (CRs) to define the chaos intent, as well as the steady state hypothesis. At a high-level, Litmus comprises of: - Chaos Control Plane: A centralized chaos management tool called chaos-center, which helps construct, schedule and visualize Litmus chaos workflows - Chaos Execution Plane Services: Made up of a chaos agent and multiple operators that execute & monitor the experiment within a defined target Kubernetes environment. !architecture summary At the heart of the platform are the following chaos custom resources: - ChaosExperiment: A resource to group the configuration parameters of a particular fault. ChaosExperiment CRs are essentially installable templates that describe the library carrying out the fault, indicate permissions needed to run it & the defaults it will operate with. Through the ChaosExperiment, Litmus supports BYOC (bring-your-own-chaos) that helps integrate (optional) any third-party tooling to perform the fault injection. - ChaosEngine: A resource to link a Kubernetes application workload/service, node or an infra component to a fault described by the ChaosExperiment. It also provides options to tune the run properties and specify the steady state validation constraints using 'probes'. ChaosEngine is watched by the Chaos-Operator, which reconciles it (triggers experiment execution) via runners. The ChaosExperiment & ChaosEngine CRs are embedded within a Workflow object that can string together one or more experiments in a desired order. - ChaosResult: A resource to hold the results of the experiment run. It provides details of the success of each validation constraint, the revert/rollback status of the fault as well as a verdict. The Chaos-exporter reads the results and exposes information as prometheus metrics. ChaosResults are especially useful during automated runs. ChaosExperiment CRs are hosted on hub.litmuschaos.io. It is a central hub where the application developers or vendors share their chaos experiments so that their users can use them to increase the resilience of the applications in production. Use cases - For Developers: To run chaos experiments during application development as an extension of unit testing or integration testing. - For CI/CD pipeline builders: To run chaos as a pipeline
Top issues
#2191Update ADOPTERS.md with Litmus usage details37 comments · 2020-10-06#2578Private git repos with SSH does not seem to work22 comments · 2021-03-19#5273DEX is not installed via helm values yaml as documented19 comments · 2025-10-24#2804Unable to connect to ChaosHub using LitmusPortal18 comments · 2021-05-14#3528x509: certifcate signed by unknown authority error when starting subscriber16 comments · 2022-03-25#5432Documentation Missing: Installing Litmus Without ChaosCenter (UI)14 comments · 2026-02-05#5033Feature Request: HTTP path filter parameter for faults12 comments · 2025-01-27#4548Add Fuzzing test suites in Litmus12 comments · 2024-03-22
Discussions
#5363where to find images?0 comments · 2025-12-28#53553.24.00 comments · 2025-12-16#53283.23.00 comments · 2025-11-17#51753.20.00 comments · 2025-08-14#51313.19.01 comments · 2025-05-19#50963.18.00 comments · 2025-04-16#50753.17.00 comments · 2025-03-17#50493.16.00 comments · 2025-02-17
Latest release
3.33.0 3.33.0 2026-10-15What's Changed fix(subscriber): resolve adminModeNamespace for chaos engine probe check by @mimo-to in https://github.com/litmuschaos/litmus/pull/5617 chore: fix the build pipeline by @Sonichigo in https://github.com/litmuschaos/litmus/pull/5624 test: add unit test for ChaosHub output mapping by @Ju-Min-Kyung in https://github.com/litmuschaos/litmus/pull/5549 test(chaoscenter): add unit tests for Loader component by @Shahazadi-Shaguftha-Syed in https://github.com/litmuschaos/litmus/pull/5567 chore: fix fuzzing test ci due to protobuf conflict by @Sonichigo in https://github.com/litmuschao