1a53f9ef28
* Added annotationCheck and fixed workflow deletion for viewer Signed-off-by: Amit Kumar Das <amitkumar.das@mayadata.io> * Minor change Signed-off-by: Amit Kumar Das <amitkumar.das@mayadata.io> |
||
|---|---|---|
| .betterci | ||
| .circleci | ||
| .github | ||
| adopters | ||
| chaos-engineering | ||
| demo | ||
| docs | ||
| hack | ||
| images | ||
| litmus-portal | ||
| monitoring | ||
| translations | ||
| .bettercodehub.yml | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| ADOPTERS.md | ||
| CHAOS_EXPERIMENT_MATURITY.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| MAINTAINERS | ||
| NOTICE.md | ||
| README.md | ||
| RELEASES.md | ||
| RELEASE_GUIDELINES.md | ||
| ROADMAP.md | ||
| fossa.md | ||
| okteto-pipeline.yaml | ||
README.md
Litmus
Cloud-Native Chaos Engineering
Read this in other languages.
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.
Getting Started with Litmus
Check out the Litmus Docs to get started.
Contributing to Chaos Hub
Check out the Contributing Guidelines for the Chaos Hub
Adopters
Check out the Adopters of LitmusChaos
(Send a PR to the above page if you are using Litmus in your chaos engineering practice)
Things to Consider
Some of the considerations that need to be made with Litmus (as a chaos framework), are broadly listed here. Many of these are already being worked on as mentioned in the ROADMAP. For details or limitations around specific experiments, refer to the respective experiments docs.
- Litmus chaos operator and the chaos experiments run as kubernetes resources in the cluster. In case of airgapped environments, the chaos custom resources and images need to be hosted on premise.
- When attempting to execute platform specific chaos experiments (like those on AWS, GCP cloud) the access details are passed via kubernetes secrets. Support for other modes of secret management with Litmus is yet to be tested/implemented.
- Some chaos experiments make use of the docker api from within the experiment pods, and thereby require the docker socket to be mounted. User discretion is advised when allowing developers/devops admins/SREs access for running these experiments.
- In (rare) cases where chaos experiments make use of privileged containers, the recommended security policies will be documented.
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.
Litmus Chaos is part of the CNCF Projects.
Community
The Litmus community meets on the third wednesday of every month at 10:00PM IST/9.30 AM PST.
Community Resources:
- Community Slack
- Sync Up Meeting Link
- Sync Up Agenda & Meeting Notes
- Youtube Channel (demos, meeting recordings, virtual meetups)
- Release Tracker
Important Links
Litmus Docs
CNCF Landscape
