diff --git a/docs/enterprise/installing-embedded-air-gap.mdx b/docs/enterprise/installing-embedded-air-gap.mdx
index 918d9cea2e..81dff4b6c6 100644
--- a/docs/enterprise/installing-embedded-air-gap.mdx
+++ b/docs/enterprise/installing-embedded-air-gap.mdx
@@ -81,6 +81,10 @@ To install with Embedded Cluster in an air gap environment:
sudo ./APP_SLUG install --license license.yaml --airgap-bundle APP_SLUG.airgap
```
Where `APP_SLUG` is the unique application slug.
+
+ :::note
+ Embedded Cluster supports installation options such as installing behind a proxy and changing the data directory used by Embedded Cluster. For the list of flags supported with the Embedded Cluster `install` command, see [Embedded Cluster Install Command Options](/reference/embedded-cluster-install).
+ :::
1. When prompted, enter a password for accessing the KOTS Admin Console.
diff --git a/docs/enterprise/installing-embedded.mdx b/docs/enterprise/installing-embedded.mdx
index e4a3e8aa7e..4e5e68d73e 100644
--- a/docs/enterprise/installing-embedded.mdx
+++ b/docs/enterprise/installing-embedded.mdx
@@ -47,6 +47,10 @@ To install an application with Embedded Cluster:
Where:
* `APP_SLUG` is the unique slug for the application.
* `LICENSE_FILE` is the customer license.
+
+ :::note
+ Embedded Cluster supports installation options such as installing behind a proxy and changing the data directory used by Embedded Cluster. For the list of flags supported with the Embedded Cluster `install` command, see [Embedded Cluster Install Command Options](/reference/embedded-cluster-install).
+ :::
1. When prompted, enter a password for accessing the KOTS Admin Console.
@@ -101,132 +105,4 @@ On the Admin Console dashboard, the application status changes from Missing to U

-[View a larger version of this image](/images/gitea-ec-ready.png)
-
-## Install Behind a Proxy Server {#proxy}
-
-The following flags can be used with the Embedded Cluster `install` command to install behind a proxy server:
-
-
| Flag | -Description | -
|---|---|
| `--http-proxy` | -Proxy server to use for HTTP | -
| `--https-proxy` | -Proxy server to use for HTTPS | -
| `--no-proxy` | -
- Comma-separated list of hosts for which not to use a proxy. -For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). -The following are never proxied: -
To ensure your app's internal cluster communication is not proxied, use fully qualified domain names like `my-service.my-namespace.svc` or `my-service.my-namespace.svc.cluster.local`. - |
-
| Flag | -Description | -
|---|---|
| `--pod-cidr` | -The range of IP addresses that can be assigned to Pods, in CIDR notation. By default, the Pod CIDR is `10.244.0.0/16`. | -
| `--service-cidr` | -The range of IP addresses that can be assigned to Services, in CIDR notation. By default, the Service CIDR is `10.96.0.0/12`. | -
| Flag | +Description | +
|---|---|
| `--admin-console-port` | +
+ Port on which to run the KOTS Admin Console. **Default**: By default, the Admin Console runs on port 30000. +**Limitation:** It is not possible to change the port for the Admin Console during a restore with Embedded Cluster. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery). + |
+
| `--airgap-bundle` | +The Embedded Cluster air gap bundle used for installations in air-gapped environments with no outbound internet access. For information about how to install in an air-gapped environment, see [Air Gap Installation with Embedded Cluster](/enterprise/installing-embedded-air-gap). | +
| `--data-dir` | +
+ The data directory used by Embedded Cluster. **Default**: `/var/lib/embedded-cluster` +**Limitations:** +
|
+
| `--http-proxy` | +
+ Proxy server to use for HTTP. + |
+
| `--https-proxy` | +
+ Proxy server to use for HTTPS. + |
+
| `--local-artifact-mirror-port` | +
+ Port on which to run the Local Artifact Mirror (LAM). **Default**: By default, the LAM runs on port 50000. + |
+
| `--no-proxy` | +
+ Comma-separated list of hosts for which not to use a proxy. +For single-node installations, pass the IP address of the node where you are installing. For multi-node installations, when deploying the first node, pass the list of IP addresses for all nodes in the cluster (typically in CIDR notation). +The following are never proxied: +
To ensure your application's internal cluster communication is not proxied, use fully qualified domain names like `my-service.my-namespace.svc` or `my-service.my-namespace.svc.cluster.local`. + |
+
| `--pod-cidr` | +
+ The range of IP addresses that can be assigned to Pods, in CIDR notation. **Default:** By default, the Pod CIDR is `10.244.0.0/16`. +**Limitation:** The `--pod-cidr` flag is not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems. + |
+
| `--service-cidr` | +
+ The range of IP addresses that can be assigned to Services, in CIDR notation. **Default:** By default, the Service CIDR is `10.96.0.0/12`. +**Limitation:** The `--service-cidr` flags is not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems. + |
+