Configuration

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

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

Initializing a configuration file

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

dkp install kommander --init > kommander.yaml

Configuring 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:

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.

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

Referencing 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.

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

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 Kommander on a small environment documentation for more information.

Install with configuration 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.

NOTE: An alternative to using the --kubeconfig=<cluster-config> flag is to initialize the KUBECONFIG environment variable. You can do this by running export KUBECONFIG=<cluster-config>. Setting your KUBECONFIG (either by flag or by environment variable) ensures that Kommander is installed on the workload cluster.

dkp install kommander --installer-config kommander.yaml --kubeconfig=<cluster-kubeconfig>

When completed, you can verify your installation.