Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport release-1.30] Document constraints of dynamic config install #4576

Merged
merged 1 commit into from
Jun 10, 2024
+7 −0
Merged

[Backport release-1.30] Document constraints of dynamic config install #4576

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/dynamic-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ In the [k0s configuration options](configuration.md) there are some options that

- `spec.api` - these options configure how the local Kubernetes API server is setup
- `spec.storage` - these options configure how the local storage (etcd or sqlite) is setup
- `spec.network.controlPlaneLoadBalancing` - these options configure how [Control Plane Load Balancing](cplb.md) is setup.

In case of HA control plane, all the controllers will need this part of the configuration as otherwise they will not be able to get the storage and Kubernetes API server running.

Expand Down Expand Up @@ -50,6 +51,12 @@ As with any Kubernetes cluster there are certain things that just cannot be chan
- `network.podCIDR`
- `network.serviceCIDR`
- `network.provider`
- `network.controlPlaneLoadBalancing`

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

Expand Down
Loading