From baa3bde31856da22adbdbebf29d6b5ac50ec46d8 Mon Sep 17 00:00:00 2001 From: SmritiSatya <117705907+SmritiSatya@users.noreply.github.com> Date: Tue, 18 Feb 2025 12:21:08 +0530 Subject: [PATCH] update Signed-off-by: Smriti Satya --- .../versioned_docs/version-3.12.0/getting-started/resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/versioned_docs/version-3.12.0/getting-started/resources.md b/website/versioned_docs/version-3.12.0/getting-started/resources.md index 7ea93bc8..0a9a9358 100644 --- a/website/versioned_docs/version-3.12.0/getting-started/resources.md +++ b/website/versioned_docs/version-3.12.0/getting-started/resources.md @@ -36,4 +36,4 @@ In Litmus, you can classify chaos infrastructure into two types: - **Self chaos infrastructure:** A chaos infrastructure that is connected to the same cluster and namespace where the ChaosCenter is deployed. You can use this to target the workloads executing on that cluster only. -- **External chaos infrastructure:** A chaos infrastructure connected to a remote Kubernetes cluster. You can operate ChaosCenter in a cross-cloud manner, connecting multiple external chaos infrastructures 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. \ No newline at end of file +- **External chaos infrastructure:** A chaos infrastructure connected to a remote Kubernetes cluster. You can operate ChaosCenter in a cross-cloud manner, connecting multiple external chaos infrastructures 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. \ No newline at end of file