Project

litmus-lite is an Apache-2.0 project under the LitmusChaos organisation. It is early: the CLI and the scenario format can still change before 1.0, and every change a user could notice is in the release notes.

• FAQ and troubleshooting: common questions, and what to do when a run does not behave.
• Roadmap: ideas that are deliberately not scheduled, and why.
• Releases: binaries, checksums and release notes.
• Issues: bugs and proposals.

Meet Pip

Pip is litmus-lite's mascot, a fledgling of the LitmusChaos Chaos Bird. Where the Chaos Bird works in goggles over a burning cluster, Pip travels light: round reading glasses, one litmus strip, and a habit of asking what should stay true before breaking anything. The strip is the LitmusChaos logo's colours, dipped.

The drawings are in docs/assets/ (pip.svg, and pip-head.svg for small sizes), under the project's Apache-2.0 licence.

What litmus-lite is not

• Not a Kubernetes chaos platform. Faults act on a laptop, a process, a container or an HTTP hop. For chaos inside clusters at scale, see LitmusChaos; move-to -adapter litmus exports a scenario to it.
• Not a load-testing tool. It runs one you already have (vegaload, k6, or your own command) alongside a fault.
• Not a sandbox. A scenario runs with your permissions. Read one you did not write before you run it.
• Not a score. A run passes or fails on hypotheses you wrote down.