Azure Install Kommander Non-air-gapped

This section provides installation instructions for the Kommander component of DKP for a non-air-gapped environment in Azure.

Prerequisites

• Ensure you have reviewed all Prerequisites for Install.

• Ensure you have a default StorageClass.

• Note the name of the cluster where you want to install Kommander. If you do not know the cluster name, use kubectl get clusters -A to display and find 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 > 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

   • Disabling the AI Navigator application

   • 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:

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

Enterprise License: Install Kommander in a Non-air-gapped Environment with DKP Catalog Applications

Enterprise License: Install Kommander 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 these values for 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"
         gitRepositorySpec:
           url: https://github.com/mesosphere/dkp-catalog-applications
           ref:
             tag: v2.7.0
   ...

   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 Customizations

You can configure the Kommander component of DKP during the initial installation, and also post-installation using the DKP CLI. If you are not sure of what you want to customize during install, then proceed to the next step. To read about Kommander component customization options, refer to this section of the documetation: Kommander Customizations

Next Step

Day 2 - Cluster Operations Management