Configure an Enterprise catalog for DKP

DKP supports configuring default catalogs for clusters with Enterprise license.

Configure a Default Enterprise Catalog

To configure DKP to use a default catalog repository, create the following YAML file:

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.4.0
CODE

Use this configuration when installing or reconfiguring DKP by passing it to the dkp install kommander command:

dkp install kommander --installer-config <config_file.yaml
CODE
  • To ensure DKP is installed on the workload cluster, use the --kubeconfig=cluster_name.conf flag as an alternative to KUBECONFIG.

  • When configuring the catalog repository post-upgrade, run dkp install kommander --init > install.yaml and update it accordingly with any custom configuration. This ensures you are using the proper default configuration values for the new DKP version.

The following section describes each label:

Label

Description

kommander.d2iq.io/project-default-catalog-repository

Indicates this acts as a Catalog Repository in all projects

kommander.d2iq.io/workspace-default-catalog-repository

Indicates this acts as a Catalog Repository in all workspaces

kommander.d2iq.io/gitapps-gitrepository-type

Indicates this Catalog Repository (and all its Applications) are certified to run on DKP

Next Step:

Configure a Custom Domain