don't make immutable the 'cluster' definition of non-HA clusters (!8679) · Merge requests · Sylva-projects / sylva-core

We had in the early days of Sylva a wrong idea that an initially single-CP-node cluster could not be upgraded to >1 CP nodes (wrong beliefs that going from 2 to 1 would necessarily lead to losing quorum, fueled by the fact that clean etcd membership removal weren't working yet at that time in RKE2 CAPI provider)... and that this would prevent doing a node rolling update... hence the conclusion to make the whole cluster top-level key immutable.

So we should not make the content of .cluster immutable on a non-HA cluster.

... and in fact, what we have today that it meant to enforce this immutability simply does not work: I've tried updates on a workload cluster single-cp-node deployment, and everything works (both for rke2 and kubeadm)

(!8399 (merged) was brought up to "fix" the interpretation ordering to fix this field...but as discussed here, we should rather remove this code which was intended to enforce a limitation, but simply is ineffective)

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Aug 18, 2026 by Thomas Morin

don't make immutable the 'cluster' definition of non-HA clusters

CI configuration

Global config for deployment pipelines

Merge request reports