Add Kaptain to DKP Catalog Applications

Add Kaptain to DKP Catalog Applications in networked environments before deploying to clusters.

NOTE: Ensure that your kubectl configuration references the cluster on which you must execute the commands.

IMPORTANT: Ensure the cluster that you want to use to deploy Kaptain is the only cluster in its workspace. Kaptain is meant to be deployed on workspaces with a single cluster.


For reference values of the required number of worker nodes, CPU, RAM, and storage resources, refer to the requirements section.


Ensure you meet all prerequisites.

NOTE: Starting from the 1.3 release, Spark Operator is no longer installed by default with Kaptain.

In case you need to run Spark jobs on Kubernetes using Spark Operator, it needs to be installed separately. Use the following instructions to install Spark Operator from Kommander Catalog DKP 2.x.

Add Kaptain to your DKP Catalog Applications via CLI

If you installed DKP with Kaptain as a workspace application in the Kommander installation file, you do not need to create a Git Repository for Kaptain.

If you added Kaptain after installing DKP, you must make it available by creating a Git Repository. Use the CLI to create the GitRepository resource and add a new repository.

Create a Git repository for Kaptain

  1. Ensure you reference the cluster on which you want to deploy Kaptain. For customers with an Essential license and a single-cluster experience, the clusterKubeconfig.conf is your Essential cluster. For customers with an Enterprise license and multi-cluster experience, your clusterKubeconfig.conf is the managed or attached cluster where you will install Kaptain.

  2. Ensure the KUBECONFIG=clusterKubeconfig.conf is set.

  3. Refer to air-gapped for DKP 2.1 or air-gapped for DKP 2.2 install instructions, if you are deploying in an air-gapped environment.

  4. Add the Flux GitRepository to your Kommander install:

    cat <<EOF | kubectl apply -f -
    kind: GitRepository
      name: kaptain-catalog-applications
      namespace: kommander
      labels: catalog dkp "true"
      interval: 1m0s
        tag: v2.0.0
      timeout: 20s
  5. Ensure the status of the GitRepository signals a ready state:

    kubectl get gitrepository kaptain-catalog-applications -n kommander

    The repository commit displays the ready state:

    NAME         URL                                                        READY   STATUS                                                              AGE
    kaptain-catalog-applications                True    Fetched revision: master/6c54bd1722604bd03d25dcac7a31c44ff4e03c6a   11m

Refer to the installation overview for next steps.