LitmusChaos Server

LitmusChaos is an open-source chaos engineering platform that tests software resilience by deliberately introducing controlled failures—such as server crashes…

  • Development
  • Infrastructure
  • Tools & Utilities
LitmusChaos is an open-source chaos engineering platform that tests software resilience by deliberately introducing controlled failures—such as server crashes or network delays—so teams can identify weaknesses before they cause real outages. The server component acts as a central hub for managing these experiments.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 25 days ago
Popular
755,739 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
701 GB minimum RAM
GitHub stars
5,739
Open issues
404
Last commit
2026-10-27
Latest release
3.33.0
License
Apache-2.0
Activity
rising

Checked 16 days ago - source: GitHub (litmuschaos/litmus)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check the ChaosEngine CRD Run the commands from the troubleshooting page to confirm the ChaosEngine custom resource definition (a Kubernetes rule that lets you describe chaos tests) exists. If it is missing, your chaos experiments cannot be created and will not run. source
  • Check chaos-operator logs If a chaos experiment fails, run the shown kubectl command, replacing the pod name, to follow the chaos-operator logs in the litmus namespace. These logs show the detailed reason the experiment did not start or apply. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should I check if chaos experiments are not being created?

Confirm that the ChaosEngine CRD exists. If the ChaosEngine custom resource definition is missing, experiments cannot be created or run.

How can I identify why a chaos experiment failed to start?

Follow the chaos-operator logs in the litmus namespace using the kubectl command from the troubleshooting page, replacing the pod name. These logs show the detailed reason the experiment did not start or apply.

What minikube initialization problem has been reported for the LitmusChaos server?

An issue reports that the server does not start after a Helm3 installation on minikube. The reported environment was Kubernetes API version 1.30, Docker, and macOS on an M2.

Where can I discuss LitmusChaos code with other users?

The GitHub Discussions forum can be used to discuss code, ask questions, and collaborate with the developer community.

Where can beginners get an introduction to the LitmusChaos interface?

A beginner-oriented Reddit post describes the resiliency focus and experiments dashboard. It helps new users understand the platform's basic interface and workflow concepts.

Answers sourced from github.com, github.com, github.com, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads