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

Go to file

Karthik Satchitanand 2fbdb4b8c6 (chore)notice: add fossa report (#1316 ) Signed-off-by: ksatchit <ksatchit@mayadata.io> Co-authored-by: ksatchit <ksatchit@mayadata.io>		2020-03-13 23:50:01 +05:30
.github	adding multiple templates for github issues (#838 )	2019-10-11 09:10:34 +05:30
adopters	Added Laura Henning as user, added success story with link to (#1314 )	2020-03-13 23:17:12 +05:30
ansiblelint/rules	(feat): Adding ansible custom lint (#1233 )	2020-03-02 22:11:40 +05:30
build	(chore)remove unused plugin files (#1276 )	2020-03-09 14:12:11 +05:30
ceps	(chore)cep: add cep template (#917 )	2019-11-06 14:23:41 +05:30
chaoslib	fix(kill-random-pod): check status only if c_iterations is defined (#1315 )	2020-03-13 23:15:39 +05:30
ci_plugins/gitlab	(fix): Fixing file extention from .yaml to .yml (#1192 )	2020-02-07 18:12:12 +05:30
contribute/developer_guide	(feat): Update the developer guide (#1181 )	2020-02-03 16:50:52 +05:30
executor	(fix): Fixing file extention from .yaml to .yml (#1192 )	2020-02-07 18:12:12 +05:30
experiments	bug-fix(experiment): Passing variable to util file (#1313 )	2020-03-13 22:36:13 +05:30
hack	feat(chaos-result): Adding failStep attribute inside chaosresult (#1270 )	2020-03-08 09:01:35 +05:30
images	Adding new images to be used for Litmus branding (#812 )	2019-10-06 17:55:19 +05:30
utils	feat(ansible-verbosity): set the head count on the basis of verbosity level (#1301 )	2020-03-13 12:25:28 +05:30
.bettercodehub.yml	(chore) add bettercodehub badge to readme (#1083 )	2020-01-09 10:41:25 +05:30
.gitignore	Add pytest suite to verify successful scaffolding of experiment artefacts (#992 )	2019-12-12 12:13:22 +05:30
.gitlab-ci.yml	(fix): Refactor Gitlab-ci yml for litmus repository (#1184 )	2020-02-03 17:37:03 +05:30
.travis.yml	(chore)ci: add sonarqube quality check (#847 )	2019-10-14 12:46:06 +05:30
ADOPTERS.md	Added Laura Henning as user, added success story with link to (#1314 )	2020-03-13 23:17:12 +05:30
CHAOS_EXPERIMENT_MATURITY.md	(chore)updates to project docs (#946 )	2019-11-15 21:19:00 +05:30
CODE_OF_CONDUCT.md	(chore)governance: update code-of-conduct and maintainers (#1312 )	2020-03-13 22:46:59 +05:30
CONTRIBUTING.md	(community)contributing_guide: include sync up meeting details (#884 )	2019-10-22 15:07:04 +05:30
GOVERNANCE.md	chore: add governance artefacts (#1272 )	2020-03-13 09:10:47 +05:30
LICENSE	(license): Update the license Authors (#957 )	2019-11-26 02:47:09 +05:30
MAINTAINERS	(chore)governance: update code-of-conduct and maintainers (#1312 )	2020-03-13 22:46:59 +05:30
Makefile	(refactor)experiments: rename experiment artefacts (#800 )	2019-10-04 20:24:12 +05:30
NOTICE.md	(chore)notice: add fossa report (#1316 )	2020-03-13 23:50:01 +05:30
README.md	Add license scan report and status (#1263 )	2020-03-09 15:54:18 +05:30
RELEASE_GUIDELINES.md	(chore)updates to project docs (#946 )	2019-11-15 21:19:00 +05:30
ROADMAP.md	(chore)roadmap: add issue links to near term roadmap items (#1285 )	2020-03-10 17:50:51 +05:30
fossa.md	(chore)notice: add fossa report (#1316 )	2020-03-13 23:50:01 +05:30
sonar-project.properties	(chore): exclude modified ansible source files from sonar analysis (#1090 )	2020-01-09 14:47:40 +05:30

README.md

Cloud-Native Chaos Engineering; Kubernetes-Native Chaos Engineering; Chaos Engineering for Kubernetes

Overview

Litmus is a toolset to do cloud-native chaos engineering. Litmus provides tools to orchestrate chaos on Kubernetes to help SREs find weaknesses in their deployments. SREs use Litmus to run chaos experiments initially in the staging environment and eventually in production to find bugs, vulnerabilities. Fixing the weaknesses leads to increased resilience of the system.

Litmus takes a cloud-native approach to create, manage and monitor chaos. Chaos is orchestrated using the following Kubernetes Custom Resource Definitions (CRDs):

ChaosEngine: A resource to link a Kubernetes application or Kubernetes node to a ChaosExperiment. ChaosEngine is watched by Litmus' Chaos-Operator which then invokes Chaos-Experiments
ChaosExperiment: A resource to group the configuration parameters of a chaos experiment. ChaosExperiment CRs are created by the operator when experiments are invoked by ChaosEngine.
ChaosResult: A resource to hold the results of a chaos-experiment. The Chaos-exporter reads the results and exports the metrics into a configured Prometheus server.

Chaos experiments 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 pipeline builders: To run chaos as a pipeline stage to find bugs when the application is subjected to fail paths in a pipeline.
For SREs: To plan and schedule chaos experiments into the application and/or surrounding infrastructure. This practice identifies the weaknesses in the system and increases resilience.

Demo

Getting Started with Litmus

See Litmus Docs.

Contributing to Chaos Hub

See Contributing to chaos hub

Adopters

See Adopters of LitmusChaos

(Send a PR to the above page if you are using Litmus in your chaos engineering practice)

License

Litmus is licensed under the Apache License, Version 2.0. See LICENSE for the full license text. Some of the projects used by the Litmus project may be governed by a different license, please refer to its specific license.

Community notes

https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q

Important Links

Litmus Docs

CNCF Landscape