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:
Prerequisites
Before installing Kommander:
Ensure you have the version of the CLI that matches the DKP version you want to install.
You have configured a Konvoy cluster using the Basic Installations for infrastructure provider specific instructions on building a cluster-based on environment.
Review the Management Cluster Application Requirements and Workspace Platform Application Defaults and Resource Requirements to ensure that your cluster has sufficient resources.
Ensure you have a default StorageClass configured.
If you want to customize your cluster’s domain or certificate, ensure you review the respective documentation sections:
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
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.