Skip to main content
Skip table of contents

Install Kommander in a Non-air-gapped Environment

To install the Kommander component of DKP in a Non-air-gapped Environment, ensure you meet the following prerequisites:


Before installing Kommander:

Install Kommander

To customize your Kommander Installer Configuration File (custom domains and certificates, HTTP proxy, Storage Class, etc.), see Kommander Additional Install Configuration for more details.

In the following command, the --kubeconfig=${CLUSTER_NAME}.conf flag ensures that you set the context to install Kommander on the right cluster. For alternatives and recommendations around setting your context, refer to Provide Context for Commands with a kubeconfig File.

Install Kommander (without a custom configuration, GPU, or other pre-installation configurations):

dkp install kommander --kubeconfig=${CLUSTER_NAME}.conf

If your environment uses HTTP/HTTPS proxies, you must include the flags --http-proxy, --https-proxy, and --no-proxy and their related values in this command for it to be successful. More information is available in Configuring an HTTP/HTTPS Proxy.

TIP: Sometimes, applications require a longer period of time to deploy, which causes the installation to time out. Add the --wait-timeout <time to wait> flag and specify a period of time (for example, 1h) to allocate more time to the deployment of applications.

Verify Installation

Once the Konvoy cluster is built and Kommander has been installed, you will want to verify your installation of Kommander in that section of documentation.

Next Step

Access the Kommander UI

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.