Install Kommander in a Pre-provisioned, Non-air-gapped Environment
Install the Kommander component of DKP in pre-provisioned, non-air-gapped environments.
Prerequisites
Ensure you have reviewed all Prerequisites for Install.
Ensure you have a default StorageClass.
Note down the name of the cluster, where you want to install Kommander. If you do not know it, use
kubectl get clusters -A
to display it.
You MUST modify the Kommander installer configuration file (kommander.yaml
) before installing the Kommander component of DKP in a pre-provisioned environment.
Create and Customize your Kommander Installer Configuration File
Set the environment variable for your cluster:
CODEexport CLUSTER_NAME=<your-management-cluster-name>
Copy the
kubeconfig
file of your Management cluster to your local directory:CODEdkp get kubeconfig -c ${CLUSTER_NAME} > ${CLUSTER_NAME}.conf
Create a configuration file for the deployment:
CODEdkp install kommander --init > kommander.yaml
Edit the installer file to include configuration overrides for the
rook-ceph-cluster
. DKP’s default configuration ships Ceph with PVC based storage which requires your CSI provider to support PVC with typevolumeMode: Block
. As this is not possible with the default local static provisioner, you can install Ceph in host storage mode.You can choose whether Ceph’s object storage daemon (osd) pods should consume all or just some of the devices on your nodes. Include one of the following Overrides:
To automatically assign all raw storage devices on all nodes to the Ceph cluster:
CODE... rook-ceph-cluster: enabled: true values: | cephClusterSpec: storage: storageClassDeviceSets: [] useAllDevices: true useAllNodes: true deviceFilter: "<<value>>" ...
To assign specific storage devices on all nodes to the Ceph cluster:
CODE... rook-ceph-cluster: enabled: true values: | cephClusterSpec: storage: storageClassDeviceSets: [] useAllNodes: true useAllDevices: false deviceFilter: "^sdb." ...
Note: If you want to assign specific devices to specific nodes using the
deviceFilter
option, refer to Specific Nodes and Devices. For general information on thedeviceFilter
value, refer to Storage Selection Settings.
If required: Customize your
kommander.yaml
.
See Kommander Customizations for customization options. Some of them include:
Custom Domains and Certificates, HTTP proxy, External Load Balancer, GPU utilization, etc.If required: If your cluster uses a custom AWS VPC and requires an internal load-balancer, set the
traefik
annotation to create an internal-facing ELB:CODE... apps: ... traefik: enabled: true values: | service: annotations: service.beta.kubernetes.io/aws-load-balancer-internal: "true ...
Expand one of the following sets of instructions, depending on your license and application environments:
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.
Next Step:
See DKP Insights if you want to enable a solution that detects current and future anomalies in workload configurations or Kubernetes clusters.