Skip to main content
Skip table of contents

Identify or Change your Default StorageClass

Kommander requires a default StorageClass.

For the supported cloud providers, the Konvoy component handles the creation of a default StorageClass.

For pre-provisioned environments, the Konvoy component handles the creation of a StorageClass in the form of a localvolumeprovisioner, which is not suitable for production use. Before installing the Kommander component, you should identify and install a Kubernetes CSI compatible storage provider that is suitable for production, and then ensure it is set as the default as shown below. See Provision a Static Local Volume for more information.

For infrastructure driver specifics, see Default Storage Providers in DKP.

Identify your StorageClass

This StorageClass is required to install Kommander.

  1. Execute the following command to verify one is configured:

    kubectl get sc --kubeconfig ${CLUSTER_NAME}.conf

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

    ebs-sc (default)   Delete          WaitForFirstConsumer   false                  41s
  2. If the desired StorageClass is not set as default, add the following annotation to the StorageClass manifest:

    annotations: "true"

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

Next Step:

Install Kommander According to your Environment

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.