Prepare the Kommander Installer Configuration File
You MUST modify the Kommander installer configuration file (
<kommander.yaml>) before installing the Kommander component of DKP.
Edit the Kommander installer configuration file to include configuration overrides for the
rook-ceph-cluster. DKP default configuration ships ceph with PVC based storage which requires your CSI provider to support PVC with type
volumeMode: 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:
rook-ceph-cluster: enabled: true values: | cephClusterSpec: storage: storageClassDeviceSets:  useAllDevices: true useAllNodes: true deviceFilter: "<<value>>"CODE
To assign specific storage devices on all nodes to the Ceph cluster:
rook-ceph-cluster: enabled: true values: | cephClusterSpec: storage: storageClassDeviceSets:  useAllNodes: true useAllDevices: false deviceFilter: "^sdb."CODE
Note: If you want to assign specific devices to specific nodes using the
deviceFilteroption, refer to Specific Nodes and Devices. For general information on the
deviceFiltervalue, refer to Storage Selection Settings.
Optional: You can add other configuration overrides to your Kommander installer configuration file, for example:
If you want to customize your cluster’s domain or certificate, review Configure custom domains and certificates during the Kommander installation.
If you require an Enterprise catalog, review Configure an Enterprise catalog.
If you require an HTTPS proxy, review Configure HTTP Proxy.
Run the following command by replacing the placeholder
<kommander.yaml>with the name of your Kommander installer configuration file:
dkp install kommander --installer-config <kommander.yaml> --wait-timeout 1hCODE
TIP: Sometimes, applications require a longer period of time to deploy, which causes the installation to time out. Add the
--wait-timeout <time to wait>flag and specify a period of time (for example,
1h) to allocate more time for the deployment of applications.