Skip to content

Commit a89330f

Browse files
authored
Add section header for 'How Litmus works?' (#387)
Signed-off-by: Aditya Ray <96347576+adi-ray@users.noreply.github.com>
1 parent c25b718 commit a89330f

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

website/docs/architecture/architecture-summary.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ The Litmus architecture can be segregated into two parts:
1414

1515
2. **Execution plane:** Contains the components required for the injection of chaos in the target resources.
1616

17+
## How Litmus works?
18+
1719
- Control plane can be used for creating and scheduling chaos experiments, which is a set of chaos faults defined in a definitive sequence to achieve desired chaos impact on the target resources upon execution. Users can log in to the ChaosCenter using the web UI or the APIs to define a chaos experiment and assess the resilience of target workloads.
1820

1921
- Once the user creates a chaos experiment using the ChaosCenter, it is passed on to the execution plane. The Execution plane can be present either in the same cluster as the ChaosCenter if the self chaos infrastructure is being used, or in a remote cluster if an external chaos infrastructure is being used. The Execution plane interprets the chaos experiment as a list of actions that will inject chaos into the target workloads. It ensures efficient orchestration of chaos in various cloud-native environments using Kubernetes custom resources.

0 commit comments

Comments
 (0)