From b1286582bac9cfbc5fe87c19ca7a19b88817c57e Mon Sep 17 00:00:00 2001 From: agyss Date: Sat, 22 Nov 2025 12:49:51 +0100 Subject: [PATCH] Clarify K3s manifest overrides and HelmChartConfig Updated notes on K3s manifests and HelmChartConfig usage. --- docs/usage/k3s.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/usage/k3s.md b/docs/usage/k3s.md index e6746af991..18cb15c3c5 100644 --- a/docs/usage/k3s.md +++ b/docs/usage/k3s.md @@ -5,8 +5,9 @@ K3s ships with lots of built-in features and services, some of which may only be ## General: K3s documentation - Automatically Deploying Manifests and Helm Charts: - - Note: `/var/lib/rancher/k3s/server/manifests` is also the path inside the K3s container filesystem, where all built-in component manifests are, so you can override them or provide your own variants by mounting files there, e.g. `--volume /path/to/my/custom/coredns.yaml:/var/lib/rancher/k3s/server/manifests/coredns.yaml` will override the packaged CoreDNS component. + - Note: `/var/lib/rancher/k3s/server/manifests` is also the path inside the K3s container filesystem, where all built-in component manifests are. These can not be overwritten, but need to be ajusted with with HelmChartConfig. - Customizing packaged Components with `HelmChartConfig`: + - Note: To extend the default traefik configuration, create a file `traefik-config.yaml` and mount it like -volume /path/to/my/custom/traefik-config.yaml:/var/lib/rancher/k3s/server/manifests/traefik-config.yaml ## CoreDNS