WARNING: 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.
kubectl on your installation machine
A DKP cluster, either one of the following, depending on your license:
An Essential cluster for customers with an Essential license
A Managed or Attached cluster for customers with an Enterprise license, in which case, said cluster has to be the only one in its workspace. D2iQ recommends that you install it on a separate attached or managed cluster, as the management cluster is intended to be a pane of glass for running other clusters and is not intended for workloads.
The following Platform applications (dependencies) enabled in the cluster where you will install Kaptain:
You have two options to install these applications. For more instructions, refer to the Install dependencies section.
Reference the cluster on which you must execute the commands. You can do this by setting the
KUBECONFIGenvironment variable to the appropriate kubeconfig file's location (
KUBECONFIG=clusterKubeconfig.conf), or by using the
--kubeconfig=cluster_name.confflag. For more information, refer to the Configure Access to Multiple Clusters documentation.
Install dependencies on any type of cluster (Essential and Enterprise)
To install any of the previous applications after you have installed DKP, follow the instructions in the Application Deployment page.
NOTE: When installing these applications, set the environment variable to the workspace of the cluster where you will install 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 Kaptain should be installed.
Install dependencies during the installation of DKP (Essential only)
You can also install the applications Kaptain requires during the installation of DKP by adapting the configuration file:
Ensure that your
kubectlconfiguration references the cluster on which you must execute the commands. For customers with an Essential license and a single-cluster experience, reference your Essential cluster.
Use the existing Kommander configuration file, or initialize the default one:
dkp install kommander --init > kommander-config.yamlCODE
Ensure the following applications are enabled in the config:
apiVersion: config.kommander.mesosphere.io/v1alpha1 kind: Installation apps: ... dex: dex-k8s-authenticator: kube-prometheus-stack: istio: knative: minio-operator: traefik: nvidia: # to enable GPU support [...]CODE
For GPU deployment, follow the instructions in Kommander GPU documentation.
Apply the new configuration to Kommander:
dkp install kommander --installer-config kommander-config.yamlCODE
This customized configuration file will enable these applications to deploy when installing DKP. For more information, refer to the Customizing the configuration file page.
Verify the deployment
Verify if the applications have been deployed successfully. For this, refer to the Verify Applications section.
Refer to the installation overview for a high level description of how to install Kaptain.