Enable DKP Catalog Applications after Installing DKP

DKP supports configuring DKP Catalog applications for environments with an Enterprise license. There are two possible ways of enabling the Enterprise catalog:

Configure a Default Enterprise Catalog after Installing DKP

1. Locate the Kommander Installer Configuration file you are using for your current deployment. This file is stored locally on your computer.
   The default file name is kommander.yaml, but your file’s name could be different.

2. Open that file and go into edit mode.

3. Enable the default catalog repository by adding the following values to your existing and already configured Kommander Installer Configuration file:

   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.6.1
   ...

4. Reconfigure DKP by reinstalling the Kommander component. In the following example, replace kommander.yaml with the name of your Kommander Installer Configuration file.
   Ensure you are using the correct name for the Kommander Installer Configuration file to maintain your clusters settings. Installing a different kommander.yaml than the one your environment is using overwrites all of your previous configurations and customizations.

   CODE

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

Tips and recommendations

• The --kubeconfig=${CLUSTER_NAME}.conf flag ensures that you install Kommander on the correct cluster. For alternatives, see Provide Context for Commands with a kubeconfig File.

• Applications can take longer to deploy, and time out the installation. 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.

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

DKP Catalog Application labels

The following section describes each label:

Next Step:

Custom Domains and Certificates for Management and Essential Clusters