AWS GPU: Install Kommander

You have installed the Konvoy component and created a cluster. Now it is time to Install Kommander which will allow you to access the UI and attach new or existing clusters to monitor.

Create and customize your Kommander Installer Configuration File

1. Set the environment variable for your cluster:

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

   CODE

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

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

   CODE

3. Create a configuration file for the deployment:

   dkp install kommander --init > kommander.yaml 

   CODE

4. If required: Customize your kommander.yaml.
   See Kommander Additional Install Configurations for customization options. Some of them include:
   Custom Domains and Certificates, HTTP proxy, External Load Balancer, GPU utilization, Rook Ceph customization (Pre-provisioned envs), etc.

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:

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

   CODE

Enable GPU Resources

1. In the same kommander.yaml file, enable Nvidia platform services.

   apps:
     nvidia-gpu-operator:
      enabled: true

   CODE

2. Append the correct Toolkit version based on your OS:

   The NVIDIA Container Toolkit allows users to run GPU accelerated containers. The toolkit includes a container runtime library and utilities to automatically configure containers to leverage NVIDIA GPU and must be configured correctly according to your base operating system.

   Centos 7.9/RHEL 7.9:
   If you’re using Centos 7.9 or RHEL 7.9 as the base operating system for your GPU enabled nodes, set the toolkit.version parameter in your Kommander Installer Configuration file or <kommander.yaml> to the following:

   kind: Installation
   apps:
     nvidia-gpu-operator:
      enabled: true
      values: |
        toolkit:
          version: v1.10.0-centos7

   CODE

   RHEL 8.4/8.6 and SLES 15 SP3
   If you’re using RHEL 8.4/8.6 or SLES 15 SP3 as the base operating system for your GPU enabled nodes, set the toolkit.version parameter in your Kommander Installer Configuration file or <kommander.yaml> to the following:

   kind: Installation
   apps:
     nvidia-gpu-operator:
      enabled: true
      values: |
        toolkit:
          version: v1.10.0-ubi8

   CODE

   Ubuntu 18.04 and 20.04
   If you’re using Ubuntu 18.04 or 20.04 as the base operating system for your GPU enabled nodes, set the toolkit.version parameter in your Kommander Installer Configuration file or <kommander.yaml> to the following:

   kind: Installation
   apps:
     nvidia-gpu-operator:
      enabled: true
      values: |
        toolkit:
          version: v1.11.0-ubuntu20.04

   CODE

Enable DKP Catalog Applications and Install Kommander

If you have an Enterprise license and would like to use the DKP Catalog Applications function, follow these steps:

1. In the same kommander.yaml of the previous section, add these values for dkp-catalog-applications:

   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"
         gitRepositorySpec:
           url: https://github.com/mesosphere/dkp-catalog-applications
           ref:
             tag: v2.5.0

   CODE

   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:

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

   CODE

Next Step:

AWS GPU: Verify Install and Log in the UI