From 86cfc1bc24cac7adf142037021f02f293b36b91f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan-Luis=20de=20Sousa-Valadas=20Casta=C3=B1o?= Date: Thu, 6 Jun 2024 12:19:11 +0200 Subject: [PATCH] Document constraints of dynamic config install MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Non-changeable fields can cause issues if not defined in the configuration file. This isn't immediately obvious by reading the docs so document it explicitly. Signed-off-by: Juan-Luis de Sousa-Valadas Castaño --- docs/dynamic-configuration.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/dynamic-configuration.md b/docs/dynamic-configuration.md index 3bbf4ce75621..a2691566e55b 100644 --- a/docs/dynamic-configuration.md +++ b/docs/dynamic-configuration.md @@ -51,6 +51,11 @@ As with any Kubernetes cluster there are certain things that just cannot be chan - `network.serviceCIDR` - `network.provider` +During the manual installation of control plane nodes with `k0s install`, all these +non-changeable options must be defined in the configuration file. This is necessary +because these fields can be used before the dynamic configuration reconciler is +initialized. Both k0sctl and k0smotron handle this without user intervention. + ## Configuration status The dynamic configuration reconciler operator will write status events for all the changes it detects. To see all dynamic config related events, use: