Install Air-gapped Kommander with DKP Catalog Applications

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

Install Kommander Air-gapped

Follow these steps:

1. Create the configuration file by running dkp install kommander --init --airgapped > kommander.yaml for the air-gapped deployment.

2. In kommander.yaml, if you are installing Kommander in an AWS VPC, set the Traefik annotation to create an internal facing ELB by setting the following:

   CODE

   apiVersion: config.kommander.mesosphere.io/v1alpha1
   kind: Installation
   apps:
     ...
     traefik:
       enabled: true
       values: |
         service:
           annotations:
             service.beta.kubernetes.io/aws-load-balancer-internal: "true"
   ...

3. In kommander.yaml, enable DKP Catalog Applications by setting the following:

   CODE

   apiVersion: config.kommander.mesosphere.io/v1alpha1
   kind: Installation
   ...
   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.5.2.tar.gz

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

5. To install the Kommander component of DKP in your air-gapped environment using the above configuration file, run the following command:

   CODE

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

   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.
   
   In the previous 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.
   

   

   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.

Next Steps:

• Verify Kommander Installation

• Log in to the UI with Kommander

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.

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

Log in to the UI

Then you will be able to log in to Kommander UI.

See Deployment of Catalog Applications in Workspaces to deploy the Catalog Applications.