Skip to content

Commit 214c5dd

Browse files
infrastructure.md
1 parent 31c8b12 commit 214c5dd

File tree

2 files changed

+2
-18
lines changed

2 files changed

+2
-18
lines changed

website/docs/concepts/infrastructure.md

+1-9
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,7 @@ With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** h
1414

1515
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.
1616

17-
## Types of Chaos Infrastructures
18-
19-
In Litmus, chaos infrastructures can be classified into two types:
20-
21-
- **Self Chaos Infrastructures:** A Chaos Infrastructure that is connected to the same cluster and namespace where the ChaosCenter is deployed. It can be used to target the workloads executing on that cluster only.
22-
23-
- **External Chaos Infrastructures:** A Chaos Infrastructure that is connected to a remote Kubernetes cluster. ChaosCenter can be operated in a cross-cloud manner, which allows connecting multiple External Chaos Infrastructure to the same ChaosCenter with the help of the [litmusctl](../litmusctl/installation.md) CLI. Once connected you can manage, monitor, observe and induce chaos from the ChaosCenter to the respective External Chaos Infrastructures.
24-
25-
### Access types
17+
## Access types
2618

2719
Chaos infrastructure can be created in two modes:
2820

website/versioned_docs/version-3.12.0/concepts/infrastructure.md

+1-9
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,7 @@ With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** h
1414

1515
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.
1616

17-
## Types of Chaos Infrastructures
18-
19-
In Litmus, chaos infrastructures can be classified into two types:
20-
21-
- **Self Chaos Infrastructures:** A Chaos Infrastructure that is connected to the same cluster and namespace where the ChaosCenter is deployed. It can be used to target the workloads executing on that cluster only.
22-
23-
- **External Chaos Infrastructures:** A Chaos Infrastructure that is connected to a remote Kubernetes cluster. ChaosCenter can be operated in a cross-cloud manner, which allows connecting multiple External Chaos Infrastructure to the same ChaosCenter with the help of the [litmusctl](../litmusctl/installation.md) CLI. Once connected you can manage, monitor, observe and induce chaos from the ChaosCenter to the respective External Chaos Infrastructures.
24-
25-
### Access types
17+
## Access types
2618

2719
Chaos infrastructure can be created in two modes:
2820

0 commit comments

Comments
 (0)