From 9df5f7472c4ca6df7b98ee3a3d43516e61bbe305 Mon Sep 17 00:00:00 2001 From: Stephan <34886888+steled@users.noreply.github.com> Date: Wed, 10 Dec 2025 06:13:43 +0100 Subject: [PATCH 1/6] Enhance installation guide for Kubermatic Helm values Updated installation instructions for Kubermatic, including support for multiple Helm values files and clarifying the order of file processing. Signed-off-by: Stephan <34886888+steled@users.noreply.github.com> --- .../installation/install-kkp-ce/_index.en.md | 21 ++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/content/kubermatic/main/installation/install-kkp-ce/_index.en.md b/content/kubermatic/main/installation/install-kkp-ce/_index.en.md index 2e8afcbb6..ba75360f5 100644 --- a/content/kubermatic/main/installation/install-kkp-ce/_index.en.md +++ b/content/kubermatic/main/installation/install-kkp-ce/_index.en.md @@ -148,8 +148,26 @@ mentioned above can be generated using any password generator or on the shell us Kubermatic Installer will suggest some properly generated secrets for you when it notices that some are missing, for example: +> **Note – Multiple Helm values files** +> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag: +> +> ```bash +> ./kubermatic-installer deploy \ +> --config kubermatic.yaml \ +> --helm-values values/defaults.yaml \ +> --helm-values values/.yaml \ +> --helm-values values/secrets.yaml +> ``` +> +> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics). +> The legacy single-file input remains supported for backward compatibility. + ```bash -./kubermatic-installer deploy --config kubermatic.yaml --helm-values values.yaml +./kubermatic-installer deploy \ + --config kubermatic.yaml \ + --helm-values values/defaults.yaml \ + --helm-values values/prod.yaml \ + --helm-values values/secrets.yaml ``` Output will be similar to this: @@ -276,6 +294,7 @@ like so: # --storageclass aws \ --config kubermatic.yaml \ --helm-values values.yaml + # If necessary, add additional --helm-values, see note above. ``` {{% notice warning %}} From 083057056d83cfdadf25540f7da5aef4be985075 Mon Sep 17 00:00:00 2001 From: Stephan <34886888+steled@users.noreply.github.com> Date: Wed, 10 Dec 2025 06:15:38 +0100 Subject: [PATCH 2/6] Enhance Helm values file instructions Updated Helm values file usage instructions for kubermatic-installer, allowing multiple files with order-based overrides. Signed-off-by: Stephan <34886888+steled@users.noreply.github.com> --- .../_index.en.md | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md b/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md index 8719ec556..daa995ccf 100644 --- a/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md +++ b/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md @@ -48,8 +48,28 @@ dex: And apply the changes to the cluster: + +> **Note – Multiple Helm values files** +> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag: +> +> ```bash +> ./kubermatic-installer deploy \ +> --config kubermatic.yaml \ +> --helm-values values/defaults.yaml \ +> --helm-values values/.yaml \ +> --helm-values values/secrets.yaml +> ``` +> +> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics). +> The legacy single-file input remains supported for backward compatibility. + + ```bash -./kubermatic-installer deploy --config kubermatic.yaml --helm-values values.yaml +./kubermatic-installer deploy \ + --config kubermatic.yaml \ + --helm-values values/defaults.yaml \ + --helm-values values/dex.yaml \ + --helm-values values/secrets.yaml ``` ## Authorization From c72d28b8b17a44e2ce70e2054450aee414a1d8f6 Mon Sep 17 00:00:00 2001 From: Stephan <34886888+steled@users.noreply.github.com> Date: Wed, 10 Dec 2025 06:20:10 +0100 Subject: [PATCH 3/6] Revise telemetry installation commands for clarity Updated installation command examples in the telemetry documentation to reflect the use of multiple Helm values files and improved formatting. Signed-off-by: Stephan <34886888+steled@users.noreply.github.com> --- .../tutorials-howtos/telemetry/_index.en.md | 27 +++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md b/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md index 35ee7dc16..90899ef5b 100644 --- a/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md +++ b/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md @@ -31,8 +31,26 @@ The `schedule` is in Cron format, please check [Cron format](https://en.wikipedi Then you can use the Kubermatic installer to install KKP by using the following command: +> **Note – Multiple Helm values files** +> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag: +> +> ```bash +> ./kubermatic-installer deploy \ +> --config kubermatic.yaml \ +> --helm-values values/defaults.yaml \ +> --helm-values values/.yaml \ +> --helm-values values/secrets.yaml +> ``` +> +> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics). +> The legacy single-file input remains supported for backward compatibility. + ```bash -./kubermatic-installer deploy --config kubermatic.yaml --helm-values values.yaml +./kubermatic-installer deploy \ + --config kubermatic.yaml \ + --helm-values values/defaults.yaml \ + --helm-values values/telemetry.yaml \ + --helm-values values/secrets.yaml ``` After this command finishes, a CronJob will be created in the `telemetry-system` namespace on the master cluster. The CronJob includes the following components: @@ -53,7 +71,12 @@ helm --namespace telemetry-system upgrade --atomic --create-namespace --install If you don’t want to send usage data to us to improve our product, or your KKP will be running in offline mode which doesn’t have access to the public Telemetry endpoint, you can disable it by using `--disable-telemetry` flag as following: ```bash -./kubermatic-installer deploy --disable-telemetry --config kubermatic.yaml --helm-values values.yaml +./kubermatic-installer deploy \ + --disable-telemetry \ + --config kubermatic.yaml \ + --helm-values values/defaults.yaml \ + --helm-values values/telemetry.yaml \ + --helm-values values/secrets.yaml ``` ## Data that Telemetry Collects From 36d0fae1151087c7ae48697f731863cbcf7d4aaa Mon Sep 17 00:00:00 2001 From: Stephan <34886888+steled@users.noreply.github.com> Date: Wed, 10 Dec 2025 06:25:38 +0100 Subject: [PATCH 4/6] Enhance MLA stack deployment instructions Updated installation instructions for the MLA stack, including support for multiple Helm values files and clarifying the order of file overrides. Signed-off-by: Stephan <34886888+steled@users.noreply.github.com> --- .../user-cluster/admin-guide/_index.en.md | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md index 928551dbf..10f471a19 100644 --- a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md +++ b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md @@ -53,8 +53,26 @@ Other parameters which can become important if you have particularly high values The MLA stack can be deployed by using the Kubermatic Installer: +> **Note – Multiple Helm values files** +> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag: +> +> ```bash +> ./kubermatic-installer deploy \ +> --config kubermatic.yaml \ +> --helm-values values/defaults.yaml \ +> --helm-values values/.yaml \ +> --helm-values values/secrets.yaml +> ``` +> +> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics). +> The legacy single-file input remains supported for backward compatibility. + ```bash -kubermatic-installer deploy usercluster-mla --config --helm-values +kubermatic-installer deploy usercluster-mla \ + --config kubermatic.yaml \ + --helm-values values/defaults.yaml \ + --helm-values values/mla.yaml \ + --helm-values values/secrets.yaml ``` Additional options that can be used for the installation include: @@ -118,6 +136,7 @@ dex: At this point, we can install the IAP Helm chart into the mla namespace as follows: ```bash +# If necessary, add additional --helm-values, see note above. kubermatic-installer deploy usercluster-mla --config --helm-values --mla-include-iap ``` @@ -507,5 +526,6 @@ kubectl delete svc cortex-store-gateway -n mla After doing the above-mentioned steps, MLA stack can be upgraded using the Kubermatic Installer: ```bash +# If necessary, add additional --helm-values, see note above. kubermatic-installer deploy usercluster-mla --config --helm-values ``` From 8d89b59b44cf727a11c78160824c7586c5199c22 Mon Sep 17 00:00:00 2001 From: Stephan <34886888+steled@users.noreply.github.com> Date: Wed, 10 Dec 2025 06:27:46 +0100 Subject: [PATCH 5/6] Revise Helm values file instructions for installation Updated Helm values file usage instructions for Kubermatic installation, emphasizing multiple file support and order of precedence. Signed-off-by: Stephan <34886888+steled@users.noreply.github.com> --- .../master-seed/installation/_index.en.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md index 6818bc4b6..22029149d 100644 --- a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md +++ b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md @@ -123,8 +123,25 @@ With this file prepared, we can now install all required charts: **Kubermatic Installer** +> **Note – Multiple Helm values files** +> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag: +> +> ```bash +> ./kubermatic-installer deploy \ +> --config kubermatic.yaml \ +> --helm-values values/defaults.yaml \ +> --helm-values values/.yaml \ +> --helm-values values/secrets.yaml +> ``` +> +> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics). +> The legacy single-file input remains supported for backward compatibility. + ```bash -./kubermatic-installer deploy seed-mla --helm-values values.yaml +./kubermatic-installer deploy seed-mla \ + --helm-values values/defaults.yaml \ + --helm-values values/seed-mla.yaml \ + --helm-values values/secrets.yaml ``` Output will be similar to this: From ced51f47afb98a738b4105b64b29687c284b4114 Mon Sep 17 00:00:00 2001 From: Stephan <34886888+steled@users.noreply.github.com> Date: Wed, 10 Dec 2025 06:31:41 +0100 Subject: [PATCH 6/6] Modify Helm values for kubermatic-seed deployment Updated Helm values file instructions for deploying the seed cluster. Signed-off-by: Stephan <34886888+steled@users.noreply.github.com> --- .../add-seed-cluster/_index.en.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md b/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md index 52cc68ae9..609b50b13 100644 --- a/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md +++ b/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md @@ -212,13 +212,30 @@ a suitable `StorageClass` and is therefore still recommended to use. Similar to how the Master Cluster can be installed with the installer, run the `deploy kubermatic-seed` command. You still need to manually ensure that the StorageClass you configured for MinIO exists already. +> **Note – Multiple Helm values files** +> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag: +> +> ```bash +> ./kubermatic-installer deploy \ +> --config kubermatic.yaml \ +> --helm-values values/defaults.yaml \ +> --helm-values values/.yaml \ +> --helm-values values/secrets.yaml +> ``` +> +> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics). +> The legacy single-file input remains supported for backward compatibility. + ```bash export KUBECONFIG=/path/to/seed-cluster/kubeconfig ./kubermatic-installer deploy kubermatic-seed \ # uncomment the line below after updating it to your respective provider; remove flag if provider is not supported or cluster is shared with master (see above) # --storageclass aws \ --config kubermatic.yaml \ - --helm-values values.yaml + --helm-values values/defaults.yaml \ + --helm-values values/seed.yaml \ + --helm-values values/secrets.yaml + ``` The command above will take care of installing/updating the CRDs, setting up MinIO and the S3-exporter and attempts