> 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/chaos-engineering/use-chaos-engineering/on-premises-smp/connect-infrastructure.md).

# Connect chaos infrastructure via proxy

This topic describes the method to connect your chaos infrastructure to the control plane on [app.harness.io](https://app.harness.io) or Self-Managed Platform (SMP) via proxy when using a [dedicated chaos infrastructure](/resilience-testing/chaos-engineering/use-chaos-engineering/infrastructure/types/legacy-infra/legacy-infra.md).

Go to configure proxy settings for [Harness Delegate Driven Chaos runner](/resilience-testing/chaos-engineering/use-chaos-engineering/infrastructure/types/ddcr/proxy-support.md#hnp-configuration-for-delegate-driven-chaos-runner-ddcr) and proxy settings for [Discovery Agent](/resilience-testing/chaos-engineering/use-chaos-engineering/infrastructure/types/ddcr/proxy-support.md#hnp-configuration-for-discovery-agent) to configure DDCR and Discovery agent related proxy settings, respectively.

{% hint style="info" %}
To know about new feature releases, enhancements, and fixed issues, go to [SMP release notes](/release-notes/self-managed-enterprise-edition.md).
{% endhint %}

To deploy a chaos infrastructure in an air-gapped cluster that accesses [app.harness.io](https://app.harness.io) or SMP control plane via proxy, configure the `HTTP_PROXY` , `HTTPS_PROXY`, and `NO_PROXY` environment variables for the subscriber, and apply the manifest, where:

* `HTTP_PROXY` is set if you deploy the SMP control plane over HTTP.
* `HTTPS_PROXY` is set if you deploy the SMP control plane over HTTPS or if you want to connect to [app.harness.io](https://app.harness.io).
* `NO_PROXY` is set with the cluster IP of the cluster where you deploy the chaos infrastructure. This allows requests to be directed to the Kube API server directly instead of going through a proxy. In addition, the proxy may not be able to connect to the Kube API server if it is deployed outside the cluster.

The above environment variables are set without providing any credentials. An example of a proxy without credentials:

```
http://<proxy-ip>:<proxy-port>
```

When the infrastructure is `CONNECTED`, an experiment is created. To stream logs in real-time during experiment execution, configure the following environment variables in the experiment manifest (for the experiment you created earlier).

Select **YAML** view in the **Experiment Builder**, and click **Edit Yaml**, and provide values for `HTTP_PROXY`, `HTTPS_PROXY`, `NO_PROXY` and `INDIRECT_UPLOAD` as shown in the diagram.

![](/files/5DS2rV3KpzyUun5oRmVV)

The environment variables are described below:

* `HTTP_PROXY` is set if you deploy the SMP control plane over HTTP.
* `HTTPS_PROXY` is set if you deploy the SMP control plane over HTTPS or if you want to connect to [app.harness.io](https://app.harness.io).
* `NO_PROXY` is set with the cluster IP of the cluster where you deploy the chaos infrastructure. This allows requests to be directed to the Kube API server directly instead of going through a proxy. In addition, the proxy may not be able to connect to the Kube API server if it is deployed outside the cluster.
* `INDIRECT_UPLOAD`is set to "true".

{% hint style="info" %}

* You can provide `HTTP_PROXY` and `HTTPS_PROXY` with endpoints that have credentials. For this, you have to first URL Encode the username and the password and provide them.
* An example of a proxy with credentials:

```
http://<url-encoded-username>:<url-encoded-password>@<proxy-ip>:<proxy-port>
```

{% endhint %}