Kommander Additional Install Configurations

You can configure the Kommander component of DKP during the initial installation, and also post-installation using the DKP CLI.

Review the Management cluster application requirements and Workspace platform application requirements to ensure that your cluster has sufficient resources.

Initialize a Kommander Installer Configuration File

To begin configuring Kommander, run the following command to initialize a default configuration file:

For a non-air-gapped environment, run this command:
CODE
```
dkp install kommander --init > kommander.yaml
```

For an air-gapped environment, run this command:

CODE

dkp install kommander --init --airgapped > kommander.yaml

If your environment uses HTTP/HTTPS proxies, you must include the flags --http-proxy, --https-proxy, and --no-proxy and their related values in these commands for them to be successful. More information is available in Configuring an HTTP/HTTPS Proxy.

Configure Applications

After you have a default configuration file, you can then configure each app either inline or by referencing another YAML file. The configuration values for each app correspond to the Helm Chart values for the application.

After the initial deployment of Kommander, you can find the application Helm Charts by checking the spec.chart.spec.sourceRef field of the associated HelmRelease:

CODE

kubectl get helmreleases <application> -o yaml -n kommander

Inline configuration (using values)

In this example, you configure the centralized-grafana application with resource limits by defining the Helm Chart values in the Kommander configuration file.

CODE

apiVersion: config.kommander.mesosphere.io/v1alpha1
kind: Installation
apps:
  centralized-grafana:
    values: |
      grafana:
        resources:
          limits:
            cpu: 150m
            memory: 100Mi
          requests:
            cpu: 100m
            memory: 50Mi
...

Reference another YAML file (using valuesFrom)

Alternatively, you could create another YAML file containing the configuration for centralized-grafana and reference that using valuesFrom. Point to this file by using either a relative path (from the configuration file location) or by using an absolute path.

CODE

cat > centralized-grafana.yaml <<EOF
grafana:
  resources:
    limits:
      cpu: 150m
      memory: 100Mi
    requests:
      cpu: 100m
      memory: 50Mi
EOF

CODE

apiVersion: config.kommander.mesosphere.io/v1alpha1
kind: Installation
apps:
  centralized-grafana:
    valuesFrom: centralized-grafana.yaml
...

Minimal Kommander Installation

You can install Kommander with a bare minimum of applications on a small environment with smaller memory, storage, and CPU requirements for testing and demo purposes. Refer to the Install DKP on a Small Environment documentation for more information.

Install with Configuration File

In the following command, the --kubeconfig=${CLUSTER_NAME}.conf flag ensures that you set the context to install Kommander on the right cluster. For alternatives and recommendations around setting your context, refer to Provide Context for Commands with a kubeconfig File.

Add the --installer-config flag to the kommander install command to use a custom configuration file. To reconfigure applications, you can also run this command after the initial installation.

CODE

dkp install kommander --installer-config kommander.yaml --kubeconfig=${CLUSTER_NAME}.conf

If your environment uses HTTP/HTTPS proxies, you must include the flags --http-proxy, --https-proxy, and --no-proxy and their related values in this command for it to be successful. More information is available in Configuring an HTTP/HTTPS Proxy.

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 to the deployment of applications.

Verify Installation

After the Konvoy cluster is built and Kommander has been installed, you will want to verify your installation of Kommander in that section of documentation.

Then you will be able to Log in to the Kommander UI.