> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure.md).

# Infrastructure

Overview of the Kubernetes, Linux, and Windows chaos infrastructure types in Harness Chaos Testing, and where to manage them in the UI.

### What you will learn <a href="#what-you-will-learn" id="what-you-will-learn"></a>

* What a chaos infrastructure is and why it is needed.
* The three supported types and how they map to the **Project Settings → Resilience Testing Infrastructures** UI.
* Where to go next to install, secure, and upgrade infrastructure.

***

### Where infrastructures live in the UI <a href="#where-infrastructures-live-in-the-ui" id="where-infrastructures-live-in-the-ui"></a>

Chaos infrastructures are managed per project under **Resilience Testing → Project Settings → Resilience Testing Infrastructures**. The page has one tab per supported type:

* **Kubernetes (Harness Infrastructure)**
* **Linux**
* **Windows**

Each infrastructure belongs to a project-scoped Harness **environment**. One environment can have multiple chaos infrastructures attached.

{% hint style="info" %}
**DEPRECATED: KUBERNETES (DEDICATED CHAOS INFRASTRUCTURE)**

You may also see a **Kubernetes (Dedicated Chaos Infrastructure)** tab. This is the legacy chaos-agent-based topology and is deprecated. New infrastructures cannot be created on it, and existing ones should be migrated to **Kubernetes (Harness Infrastructure)** (the DDCR flow) when possible.
{% endhint %}

{% hint style="info" %}
**DELETING ENVIRONMENTS**

To delete an environment, first detach or delete every chaos infrastructure attached to it. The environment delete will fail while a referenced infrastructure exists.
{% endhint %}

***

### Environment and infrastructure scope <a href="#environment-and-infrastructure-scope" id="environment-and-infrastructure-scope"></a>

Resilience Testing uses only project-level environments and infrastructures. Create the environment and the chaos infrastructure in the project where you run experiments.

* **Creating an infrastructure:** The environment picker displays **Project**, **Organization**, and **Account** tabs, but only a project environment can be applied. Selecting an organization or account environment displays a warning that only project-scoped environments are supported, and clears the field.
* **Creating an experiment:** The **New Experiment** screen lists only the environments and chaos infrastructures in the current project. An environment or infrastructure created at the organization or account level does not appear. This is expected behavior.

Environments and infrastructures are Harness platform objects shared with other modules. Organization and account scope exist for those modules; Resilience Testing does not use them.

***

### Supported infrastructure types <a href="#supported-infrastructure-types" id="supported-infrastructure-types"></a>

Harness Chaos Testing supports three chaos infrastructure types. **Kubernetes** is recommended for all new setups; the others cover non-Kubernetes targets.

| Type           | Target                                               | Doc                                                                                                                                |
| -------------- | ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Kubernetes** | Kubernetes clusters, via the Harness Delegate (DDCR) | [Set up Kubernetes infrastructure](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/kubernetes.md) |
| **Linux**      | Linux VMs and Cloud Foundry                          | [Linux infrastructure](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/linux.md)                  |
| **Windows**    | Windows VMs                                          | [Windows infrastructure](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/windows.md)              |

Chaos experiments against AWS, GCP, Azure, VMware, and bare-metal targets run **on top of** a Kubernetes chaos infrastructure (the runner pods execute there even when the fault hits a non-Kubernetes resource). Cloud Foundry experiments run on Linux infrastructure.

***

### Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

<details>

<summary>An organization-level environment or infrastructure does not appear on the New Experiment screen</summary>

The behavior is expected. Chaos experiments use only environments and infrastructures in the current project. Create a project environment, then create the chaos infrastructure in that environment under **Project Settings → Resilience Testing Infrastructures**.

</details>

***

### Next steps <a href="#next-steps" id="next-steps"></a>

* [Set up Kubernetes infrastructure](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/kubernetes.md): install the Delegate-driven runner and connect a target cluster.
* [Cluster permissions](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/kubernetes/permissions.md): review the Kubernetes RBAC the chaos service account needs.
* [Network configuration](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/kubernetes/network-config.md): mTLS and Harness Network Proxy (HNP) settings for Kubernetes chaos infrastructure.
* [Upgrade Linux infrastructure](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/linux/upgrade.md): upgrade an existing Linux install across releases.
* [Upgrade Windows infrastructure](https://developer.harness.io/resilience-testing/3.0/chaos-testing/infrastructure/windows/upgrade.md): upgrade an existing Windows install across releases.

Before creating an infrastructure, [create an environment](https://developer.harness.io/resilience-testing/chaos-engineering/chaos-experiments/create-experiments.md#create-environment). A chaos infrastructure always lives inside an environment.

{% @harness-feedback/feedback %}
