LitmusChaos Frontend

LitmusChaos Frontend is the web interface for the open-source LitmusChaos platform, giving operations teams a browser-based way to create, monitor, and manage…

  • Development
  • Infrastructure
  • Tools & Utilities
LitmusChaos Frontend is the web interface for the open-source LitmusChaos platform, giving operations teams a browser-based way to create, monitor, and manage Kubernetes chaos 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,747 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
701 GB minimum RAM
GitHub stars
5,747
Open issues
427
Last commit
2026-10-27
Latest release
3.33.0
License
Apache-2.0
Activity
declining

Checked 3 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 first Before creating chaos, run the listed check commands to confirm the ChaosEngine custom resource definition is installed in the cluster. Without it, the cluster does not understand the chaos objects you are trying to create. source
  • Read the chaos-operator logs if something fails If a chaos object is not created, follow the chaos-operator pod logs in the litmus namespace. That pod is the worker that applies your chaos settings, and its logs usually show the exact reason the request failed. source
  • Use the HTTP probe example for URL checks If an experiment should keep testing a web address, use the HTTP GET probe example and set the URL, response-code check, and timing values. This lets Litmus verify the service stays reachable while chaos is running. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does the Litmus portal frontend not load during local development?

Port-forward the litmus-portal frontend and litmus-portal server services after installation. When they are available on ports 3000 and 8080, run npm start to access the local development server.

Can Litmus integrate optional third-party tools for fault injection?

Yes. ChaosExperiment CRs describe the fault library, permissions, and defaults, and support bringing your own chaos to integrate third-party tooling.

Can Litmus be used in air-gapped environments?

The Litmus docs include an Air Gapped section covering how Litmus can be used in air-gapped environments and enterprises.

Where are Litmus chaos experiment results recorded?

Litmus uses a ChaosResult resource to hold the results of an experiment run. It includes validation-constraint success, revert/rollback status, and a verdict.

Answers sourced from docs.litmuschaos.io, github.com, github.com

Community

Collected 48 days ago - public community threads