Changes (infrastructure.md)

andoriyaprashant · andoriyaprashant · commit 31c8b124b42a · 2024-11-29T10:15:37.000+05:30
Signed-off-by: andoriyaprashant &lt;prashantandoriya@gmail.com&gt;
diff --git a/website/docs/concepts/chaos-center.md b/website/docs/concepts/chaos-center.md
@@ -26,14 +26,5 @@ ChaosCenter gives you access to a plethora of features, the major ones include:
   - Rolling out automated changes using GitOps
   - Allowing image addition from custom image server (both public and private)
   - Measure and analyze the Resilience Score of each chaos scenario
+  
 
-## Chaos Infrastructures
-Chaos infrastructure is a service that runs in your target environment and aids Litmus in accessing and injecting chaos to your target environment. There should always be at least one or more than one chaos infrastructure connected to the ChaosCenter to execute an experiment.
-
-## Types of Chaos Infrastructures
-
-In Litmus, chaos infrastructures can be classified into two types:
-
-- **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.
-
-- **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.
diff --git a/website/docs/concepts/chaos-workflow.md b/website/docs/concepts/chaos-workflow.md
@@ -25,7 +25,7 @@ The term **Chaos Scenario/Workflow** has been changed to **Chaos Experiment**.
 The following are required before creating a Chaos Experiment:
 
 - [ChaosCenter](../concepts/chaos-center.md#chaoscenter)
-- [Chaos Infrastructure](../concepts/chaos-center.md#chaos-infrastructures)
+- [Chaos Infrastructure](../concepts/infrastructure.md#chaos-infrastructures)
 - [Probes](probes.md)
 
 ## Defining and executing a chaos experiment
diff --git a/website/docs/concepts/infrastructure.md b/website/docs/concepts/infrastructure.md
@@ -14,6 +14,14 @@ With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** h
 
 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.
 
+## Types of Chaos Infrastructures
+
+In Litmus, chaos infrastructures can be classified into two types:
+
+- **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.
+
+- **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.
+
 ### Access types
 
 Chaos infrastructure can be created in two modes:
diff --git a/website/docs/user-guides/chaos-infrastructure-installation.md b/website/docs/user-guides/chaos-infrastructure-installation.md
@@ -8,7 +8,7 @@ sidebar_label: Chaos Infrastructure Installation
 
 ## Prerequisites
 
-- Before connecting a Chaos Infrastructure to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), learn about what is a [Chaos Infrastructure](../concepts/chaos-center.md#chaos-infrastructures) in Litmus.
+- Before connecting a Chaos Infrastructure to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), learn about what is a [Chaos Infrastructure](../concepts/infrastructure.md#chaos-infrastructures) in Litmus.
 - Make sure [litmusctl](../litmusctl/installation.md) is installed.
 
 ## Connecting Chaos Infrastructure
diff --git a/website/docs/user-guides/uninstall-litmus.md b/website/docs/user-guides/uninstall-litmus.md
@@ -8,7 +8,7 @@ sidebar_label: Uninstall Litmus
 
 ## Chaos Infrastructure
 
-To disconnect the [Chaos Infrastructure](../concepts/chaos-center.md#chaos-infrastructures) connected to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), follow these steps:
+To disconnect the [Chaos Infrastructure](../concepts/infrastructure.md#chaos-infrastructures) connected to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), follow these steps:
 
 1. Remove the ChaosEngines of the respective Chaos Infrastructure
 
diff --git a/website/versioned_docs/version-3.12.0/concepts/chaos-center.md b/website/versioned_docs/version-3.12.0/concepts/chaos-center.md
@@ -26,14 +26,3 @@ ChaosCenter gives you access to a plethora of features, the major ones include:
   - Rolling out automated changes using GitOps
   - Allowing image addition from custom image server (both public and private)
   - Measure and analyze the Resilience Score of each chaos scenario
-
-## Chaos Infrastructures
-Chaos infrastructure is a service that runs in your target environment and aids Litmus in accessing and injecting chaos to your target environment. There should always be at least one or more than one chaos infrastructure connected to the ChaosCenter to execute an experiment.
-
-## Types of Chaos Infrastructures
-
-In Litmus, chaos infrastructures can be classified into two types:
-
-- **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.
-
-- **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.
diff --git a/website/versioned_docs/version-3.12.0/concepts/chaos-workflow.md b/website/versioned_docs/version-3.12.0/concepts/chaos-workflow.md
@@ -25,7 +25,7 @@ The term **Chaos Scenario/Workflow** has been changed to **Chaos Experiment**.
 The following are required before creating a Chaos Experiment:
 
 - [ChaosCenter](../concepts/chaos-center.md#chaoscenter)
-- [Chaos Infrastructure](../concepts/chaos-center.md#chaos-infrastructures)
+- [Chaos Infrastructure](../concepts/infrastructure.md#chaos-infrastructures)
 - [Probes](probes.md)
 
 ## Defining and executing a chaos experiment
diff --git a/website/versioned_docs/version-3.12.0/concepts/infrastructure.md b/website/versioned_docs/version-3.12.0/concepts/infrastructure.md
@@ -14,6 +14,14 @@ With the latest release of LitmusChaos 3.0.0 the term **Chaos Delegate/Agent** h
 
 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.
 
+## Types of Chaos Infrastructures
+
+In Litmus, chaos infrastructures can be classified into two types:
+
+- **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.
+
+- **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.
+
 ### Access types
 
 Chaos infrastructure can be created in two modes:
diff --git a/website/versioned_docs/version-3.12.0/user-guides/chaos-infrastructure-installation.md b/website/versioned_docs/version-3.12.0/user-guides/chaos-infrastructure-installation.md
@@ -8,7 +8,7 @@ sidebar_label: Chaos Infrastructure Installation
 
 ## Prerequisites
 
-- Before connecting a Chaos Infrastructure to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), learn about what is a [Chaos Infrastructure](../concepts/chaos-center.md#chaos-infrastructures) in Litmus.
+- Before connecting a Chaos Infrastructure to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), learn about what is a [Chaos Infrastructure](../concepts/infrastructure.md#chaos-infrastructures) in Litmus.
 - Make sure [litmusctl](../litmusctl/installation.md) is installed.
 
 ## Connecting Chaos Infrastructure
diff --git a/website/versioned_docs/version-3.12.0/user-guides/uninstall-litmus.md b/website/versioned_docs/version-3.12.0/user-guides/uninstall-litmus.md
@@ -8,7 +8,7 @@ sidebar_label: Uninstall Litmus
 
 ## Chaos Infrastructure
 
-To disconnect the [Chaos Infrastructure](../concepts/chaos-center.md#chaos-infrastructures) connected to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), follow these steps:
+To disconnect the [Chaos Infrastructure](../concepts/infrastructure.md#chaos-infrastructures) connected to the [ChaosCenter](../concepts/chaos-center.md#chaoscenter), follow these steps:
 
 1. Remove the ChaosEngines of the respective Chaos Infrastructure
 
