32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
---
|
|
id: chaos-infrastructure
|
|
title: Chaos infrastructure
|
|
sidebar_label: Chaos Infrastructure
|
|
---
|
|
|
|
Chaos infrastructure is a service that runs in your target environment and aids the Litmus control plane in accessing and injecting chaos at a cloud-native scale. All the chaos infrastructure services adhere to the principle of least privilege, where the services execute with the minimum number of required permissions. A chaos infrastructure can be created under a Chaos Environment.
|
|
|
|
:::note
|
|
With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** has been changed to **Chaos Infrastructure**.
|
|
:::
|
|
|
|
## Chaos environment
|
|
|
|
An environment represents where you are installing your chaos infrastructure and acts as an additional level of abstraction for the same. You categorize each environment as prod or non-prod.
|
|
|
|
### Access types
|
|
|
|
Chaos infrastructure can be created in two modes:
|
|
|
|
- **Cluster Wide:** This mode of infrastructure installation allows targeting resources across the entire cluster, in all the namespaces, as part of an experiment.
|
|
- **Namespace Mode:** This mode of infrastructure installation allows targeting resources only in the namespace where the chaos infrastructure is deployed.
|
|
|
|
:::note
|
|
- There can only be one cluster-wide chaos infrastructure per cluster.
|
|
- There may be multiple namespace-scoped chaos infrastructures per cluster.
|
|
:::
|
|
|
|
## Learn more
|
|
|
|
- [How to connect a Chaos Infrastructure](../user-guides/chaos-infrastructure-installation.md)
|