> 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/troubleshooting-and-resources/whats-supported.md).

# What's supported

This topic lists the platforms and technologies that Harness Chaos Engineering supports for deploying chaos infrastructure and running chaos experiments.

Harness Chaos Engineering is supported on the following deployment models:

* [Harness SaaS](#harness-saas)
* [Self-Managed Enterprise Edition](#self-managed-enterprise-edition)
* [Self-Managed Enterprise Edition in Offline Environments](#self-managed-enterprise-edition-in-offline-environments)

Harness Chaos Engineering supports running faults on [AWS](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md), [Azure](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md), [GCP](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/gcp/gcp.md), [Kubernetes](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md), [Linux](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md), [VMware](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md), and [Windows](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md) platforms.

***

### Harness SaaS <a href="#harness-saas" id="harness-saas"></a>

**Harness SaaS** is a fully managed cloud service that provides:

* **Quick setup** - start in minutes
* **Automatic updates** and maintenance
* **Global availability** with 99.9% uptime SLA
* **Enterprise ChaosHub** access included

#### Supported Platforms for Chaos Infrastructure <a href="#supported-platforms-for-chaos-infrastructure" id="supported-platforms-for-chaos-infrastructure"></a>

The following table shows the supported operating systems and distributions for deploying chaos infrastructure:

| Platform       | Distribution             | Version   | Supported |
| -------------- | ------------------------ | --------- | --------- |
| **Kubernetes** | Amazon EKS               | k8s 1.21+ | ✅         |
| **Kubernetes** | Azure AKS                | k8s 1.21+ | ✅         |
| **Kubernetes** | Google GKE               | k8s 1.21+ | ✅         |
| **Kubernetes** | Red Hat OpenShift        | k8s 1.21+ | ✅         |
| **Kubernetes** | Rancher                  | k8s 1.21+ | ✅         |
| **Kubernetes** | VMware Tanzu             | k8s 1.21+ | ✅         |
| **Kubernetes** | Self-managed clusters    | k8s 1.21+ | ✅         |
| **Linux**      | Ubuntu                   | 16.04+    | ✅         |
| **Linux**      | Red Hat Enterprise Linux | 7+        | ✅         |
| **Linux**      | CentOS                   | 7+        | ✅         |
| **Linux**      | Debian                   | 10+       | ✅         |
| **Linux**      | Fedora                   | 30+       | ✅         |
| **Linux**      | openSUSE Leap            | 15.4+     | ✅         |

{% hint style="info" %}
**CONTAINER RUNTIMES**

Kubernetes faults work with **Docker**, **CRI-O**, and **containerd** runtimes.
{% endhint %}

#### Supported Chaos Fault Categories <a href="#supported-chaos-fault-categories" id="supported-chaos-fault-categories"></a>

The following table shows available fault types and where they are supported. For a complete list and detailed information, go to [Chaos faults](/resilience-testing/chaos-engineering/faults/chaos-fault-categories/chaos-faults-reference.md).

| Fault type                                                                               | Linux | K8s | Windows | VMware | AWS | GCP | Azure |
| ---------------------------------------------------------------------------------------- | ----- | --- | ------- | ------ | --- | --- | ----- |
| <p><strong>Network</strong><br>Network loss, Network latency, etc.</p>                   | ✅     | ✅   | ✅       | ✅      | ✅   |     |       |
| <p><strong>HTTP</strong><br>HTTP latency, HTTP modify body, etc.</p>                     |       | ✅   |         | ✅      | ✅   |     |       |
| <p><strong>DNS</strong><br>DNS error, DNS spoof, etc.</p>                                | ✅     | ✅   | ✅       | ✅      | ✅   |     |       |
| <p><strong>System time</strong><br>Time skew chaos, etc.</p>                             | ✅     | ✅   |         |        |     |     |       |
| <p><strong>Resource stress</strong><br>CPU stress, Memory stress, etc.</p>               | ✅     | ✅   | ✅       | ✅      | ✅   |     | ✅     |
| <p><strong>State change</strong><br>VM stop, Pod kill, etc.</p>                          | ✅     | ✅   | ✅       | ✅      | ✅   | ✅   | ✅     |
| <p><strong>Managed Services</strong><br>AWS ECS agent stop, Azure web app stop, etc.</p> |       |     |         |        | ✅   | ✅   | ✅     |

***

### Self-Managed Enterprise Edition <a href="#self-managed-enterprise-edition" id="self-managed-enterprise-edition"></a>

**Self-Managed Enterprise Edition** provides on-premises deployment with:

* **Full control** over your deployment
* **Enterprise integrations** (LDAP, SSO)
* **Custom security policies** and compliance
* **All SaaS features** in feature parity

#### Limitations <a href="#limitations" id="limitations"></a>

Chaos Engineering on Self-Managed Enterprise Edition has the following limitations compared to SaaS:

* **Harness Enterprise ChaosHub** is not connected by default
  * Contact [Harness Support](mailto:support@harness.io) for access to the Enterprise ChaosHub
  * Git-based custom ChaosHubs are no longer supported. Use [Templates](/resilience-testing/chaos-testing/templates.md) to manage reusable chaos artifacts.
* **Harness AI** for CE

#### Supported Platforms <a href="#supported-platforms" id="supported-platforms"></a>

All platforms and fault categories supported in [Harness SaaS](#harness-saas) are also supported in Self-Managed Enterprise Edition.

For more information about deployment, go to [Self-Managed Enterprise Edition and CE on SMP](/resilience-testing/shared-capabilities/on-premises-smp.md).

***

### Self-Managed Enterprise Edition in Offline Environments <a href="#self-managed-enterprise-edition-in-offline-environments" id="self-managed-enterprise-edition-in-offline-environments"></a>

**Self-Managed Enterprise Edition in Offline Environments** provides:

* **Completely isolated** from external networks
* **Air-gapped deployment** support
* **All enterprise features** available
* **Custom security policies** and compliance

#### Requirements <a href="#requirements" id="requirements"></a>

* **Templates** integration required for fault templates (Git-based custom ChaosHubs are no longer supported)
* **Contact support** for Enterprise ChaosHub access in offline environments

#### Supported Platforms <a href="#supported-platforms" id="supported-platforms"></a>

All CE features and platforms supported in [Self-Managed Enterprise Edition](#self-managed-enterprise-edition) are also supported in offline environments.

***

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

1. [**Learn key concepts**](/resilience-testing/new-to-resilience-testing/key-concepts.md) - Understand chaos engineering fundamentals
2. [**Start with chaos testing**](/resilience-testing/chaos-testing/get-started.md) - Run your first chaos experiment
3. [**Explore integrations**](/resilience-testing/shared-capabilities/integrations/cicd/jenkins.md) - Connect with your existing tools

{% hint style="info" %}
**READY TO GET STARTED?**

Check out our [**Get Started Guide**](/resilience-testing/chaos-testing/get-started.md) to begin your chaos engineering journey.
{% endhint %}