Add Kaptain to DKP Catalog Applications in networked environments before deploying to clusters
Ensure that your
kubectl configuration references the cluster on which you must execute the commands.
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 have reviewed and executed all steps in the prerequisites section.
Create a Git repository for Kaptain
Make Kaptain available for deployment by creating a Git Repository. Use the CLI to create the
GitRepository resource and add a new repository.
Refer to air-gapped for DKP 2.2 and later install instructions, if you are deploying in an air-gapped environment.
clusterKubeconfig.confis set to your Essential or Management cluster depending on your license.
Add the Flux
GitRepositoryto your Kommander install:
cat <<EOF | kubectl apply -f - apiVersion: source.toolkit.fluxcd.io/v1beta1 kind: GitRepository metadata: name: kaptain-catalog-applications namespace: kommander labels: kommander.d2iq.io/gitrepository-type: catalog kommander.d2iq.io/gitapps-gitrepository-type: dkp kommander.d2iq.io/workspace-default-catalog-repository: "true" spec: interval: 1m0s ref: tag: v2.1.0 timeout: 20s url: https://github.com/mesosphere/kaptain-catalog-applications EOFCODE
Ensure the status of the
GitRepositorysignals a ready state:
kubectl get gitrepository kaptain-catalog-applications -n kommanderCODE
The repository commit displays the ready state:
NAME URL READY STATUS AGE kaptain-catalog-applications https://github.com/mesosphere/kaptain-catalog-applications True Fetched revision: master/6c54bd1722604bd03d25dcac7a31c44ff4e03c6a 11mCODE