You can configure the Kommander component of DKP during the initial installation, and also post-installation using the DKP CLI.
Initialize a Configuration File
To begin configuring Kommander, run the following command to initialize a default configuration file:
dkp install kommander --init > kommander.yaml
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
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 ...
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.
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 DKP on a Small Environment documentation for more information.
Install with Configuration File
--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.
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>
If your environment uses HTTP/HTTPS proxies, you must include the flags
--no-proxy and their related values in this command for it to be successful. More information is available in Configure HTTP 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 for the deployment of applications.
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 in to Kommander UI.