{"repo":"litmuschaos/litmus","free":true,"listed":false,"github":"https://github.com/litmuschaos/litmus","clone":"git clone https://github.com/litmuschaos/litmus.git","description":"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","language":"Go","stars":5597,"topics":["chaos-engineering","kubernetes","chaos-experiments","cloud-native","chaoshub","hacktoberfest","cncf","operator-sdk","site-reliability-engineering","golang"],"license":"Apache-2.0","category":"deployment-docker-iac","readme_excerpt":"LitmusChaos Open Source Chaos Engineering Platform Read this in other languages. 🇰🇷 🇨🇳 🇧🇷 🇮🇳 🇪🇸 Overview LitmusChaos is an open source Chaos Engineering platform that enables teams to identify weaknesses & potential outages in infrastructures by inducing chaos tests in a controlled way. Developers & SREs can practice Chaos Engineering with LitmusChaos as it is easy to use, based on modern Chaos Engineering principles & community collaborated. It is 100% open source & a CNCF project. LitmusChaos takes a cloud-native approach to create, manage and monitor chaos. The platform itself runs as a set of microservices and uses Kubernetes custom resources (CRs) to define the chaos intent, as well as the steady state hypothesis. At a high-level, Litmus comprises of: - Chaos Control Plane : A centralized chaos management tool called chaos-center, which helps construct, schedule and visualize Litmus chaos workflows - Chaos Execution Plane Services : Made up of a chaos agent and multiple operators that execute & monitor the experiment within a defined target Kubernetes environment. At the heart of the platform are the following chaos custom resources: - ChaosExperiment : A resource to group the configuration parameters of a particular fault. ChaosExperiment CRs are essentially installable templates that describe the library carrying out the fault, indicate permissions needed to run it & the defaults it will operate with. Through the ChaosExperiment, Litmus supports BYOC (bring-y","default_branch":null,"files":null,"tree":[],"storefront":"/r/litmuschaos","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/litmuschaos/litmus/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}