Install Kommander in an Air-gapped Environment

Follow these steps to install the Kommander component of DKP in an air-gapped environment.

Prerequisites

• Ensure you have reviewed all Prerequisites for Install.

• Ensure you have a default StorageClass.

• Ensure you have loaded all necessary images for your configuration. See Load the Images into Your Registry: Air-gapped Environments.

• Note down the name of the cluster, where you want to install Kommander. If you do not know it, use kubectl get clusters -A to display it.

Create your Kommander Installer Configuration File

1. Set the environment variable for your cluster:

   CODE

   export CLUSTER_NAME=<your-management-cluster-name>

2. Copy the kubeconfig file of your Management cluster to your local directory:

   CODE

   dkp get kubeconfig -c ${CLUSTER_NAME} > ${CLUSTER_NAME}.conf

3. Create a configuration file for the deployment:

   CODE

   dkp install kommander --init --airgapped > kommander.yaml

4. If required, customize your kommander.yaml.
   See Kommander Customizations for customization options. Some of them include:

   • Custom Domains and Certificates

   • HTTP proxy

   • External Load Balancer

   • GPU utilization, etc.

   • Rook Ceph customization for Pre-provisioned environments

5. If required: If your cluster uses a custom AWS VPC and requires an internal load-balancer, set the traefik annotation to create an internal-facing ELB:

   CODE

   ...
   apps:
     traefik:
       enabled: true
       values: |
         service:
           annotations:
             service.beta.kubernetes.io/aws-load-balancer-internal: "true
   ...

6. Expand one of the following sets of instructions, depending on your license and application environments:

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.

dkp install kommander \
--installer-config kommander.yaml --kubeconfig=${CLUSTER_NAME}.conf \
--kommander-applications-repository ./application-repositories/kommander-applications-v2.6.1.tar.gz \
--charts-bundle ./application-charts/dkp-kommander-charts-bundle-v2.6.1.tar.gz 

Enterprise License: Install Kommander in an Air-gapped Environment with DKP Catalog Applications

Enterprise License: Install Kommander in an Air-gapped Environment with DKP Catalog Applications

If you want to enable DKP Catalog applications after installing DKP, see Enable DKP Catalog Applications after Installing DKP.

1. In the same kommander.yaml of the previous section, add the following values to enable DKP Catalog Applications:

   CODE

   ...
   catalog:
     repositories:
       - name: dkp-catalog-applications
         labels:
           kommander.d2iq.io/project-default-catalog-repository: "true"
           kommander.d2iq.io/workspace-default-catalog-repository: "true"
           kommander.d2iq.io/gitapps-gitrepository-type: "dkp"
         path: ./dkp-catalog-applications-v2.6.1.tar.gz
   ...

   If you only want to enable catalog applications to an existing configuration, add these values to an existing installer configuration file to maintain your Management cluster’s settings.

2. Use the customized kommander.yaml to install DKP:

   CODE

   dkp install kommander \
   --installer-config kommander.yaml --kubeconfig=${CLUSTER_NAME}.conf \
   --kommander-applications-repository ./application-repositories/kommander-applications-v2.6.1.tar.gz \
   --charts-bundle ./application-charts/dkp-kommander-charts-bundle-v2.6.1.tar.gz \
   --charts-bundle ./application-charts/dkp-catalog-applications-charts-bundle-v2.6.1.tar.gz

Tips and recommendations

• The --kubeconfig=${CLUSTER_NAME}.conf flag ensures that you install Kommander on the correct cluster. For alternatives, see Provide Context for Commands with a kubeconfig File.

• Applications can take longer to deploy, and time out the installation. 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.

• If the Kommander installation fails, or you wish to reconfigure applications, rerun the install command to retry.

Next Step:

Verify Kommander Installation

See DKP Insights if you want to enable a solution that detects current and future anomalies in workload configurations or Kubernetes clusters.