Prerequisites

Before installing Kommander:

Configure a Default StorageClass

The cluster where Kommander is installed must have a default StorageClass configured. Use the following command to verify one is configured:

kubectl get sc
CODE

The output should look similar to this. Note the (default) after the name:

NAME               PROVISIONER       RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
ebs-sc (default)   ebs.csi.aws.com   Delete          WaitForFirstConsumer   false                  41s
CODE

If the desired StorageClass is not set as default, add the following annotation to the StorageClass manifest:

annotations:
  storageclass.kubernetes.io/is-default-class: "true"
CODE

More information on setting a StorageClass as default can be found at Changing the default storage class in the Kubernetes documentation.

Install Kommander

To customize your Kommander installation, see the Kommander Install Configuration for more details.

Before running the commands below, ensure that your kubectl configuration references the cluster on which you want to install Kommander, otherwise it will install on the bootstrap cluster. You can do this by setting the KUBECONFIG environment variable to the appropriate kubeconfig file’s location.

NOTE: An alternative to initializing the KUBECONFIG environment variable as stated earlier is to use the --kubeconfig=cluster_name.conf flag. This ensures that Kommander is installed on the correct cluster.

Install Kommander:

dkp install kommander
CODE

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.

For other environments, see the section of documentation called Advanced Kommander Configuration.

Next Step

Log in to the UI with Kommander