CI: regression in "add a new dynamic disabled unit option 🔴" (!6917) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Add a new dynamic disabled unit option in CI framework, if we add a 🔴 emoji in our pipeline name the key behind will be parse as unit that need to be disabled with:

units:
  <unit-name>:
    enabled: false

Similar to dynamic enabled unit option, this avoid to create new CI values files for each units we need to test

Allowed pattern is:

🔴 mgmt:<unit-name>, wkld:<unit-name>,<unit-name>

if a prefix mgmt: or wkld: is set the option will be applied only to the related cluster. Otherwise it will be applied to both.

this version is also more flexible: it allows to use in list of enabled/disabled units

closes #3547 (closed)

Test coverage

in the pipeline 2324588379

we have tested the following cases:

case A: 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu 🛠️ misc 🟢 neuvector , mgmt : harbor, wkld :velero

Management cluster

results of py script:
resulting values.yaml:
- harbor enabled
- neuvector enabled

Workload cluster:

results of py script:
resulting values.yml:
- neuvector enabled
- velero enabled

case B: 🎬 preview ☁️ capo 🚀 rke2 🐧 suse 🛠️ misc 🟢 neuvector 🔴 neuvector , velero

Management cluster:

results of py script:
resulting values.yaml:
- neuvector disabled
- velero disabled

Workload cluster:

results of py script:
resulting values.yml:
- neuvector disabled
- velero disabled

case C: 🎬 preview ☁️ capo 🚀 rke2 🐧 suse 🛠️ misc 🟢 neuvector, harbor 🔴 neuvector , velero

Management cluster:

results of py script:
resulting values.yaml:

Workload cluster:

results of py script:
resulting values.yml:

case D: 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu 🛠️ misc 🟢 🔴

Management cluster:

results of py script:
resulting values.yaml: (similar to legacy deployment without any disabled/enabled units)
- units

Workload cluster: (pipeline canceled to save CI resources)

case E: 🎬 preview ☁️ capo 🚀 rke2 🐧 suse 🛠️ misc 🔴 neuvector, velero, mgmt: harbor

Management cluster:

results of py script:
resulting values.yaml:

Workload cluster:

results of py script:
resulting values.yml:

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	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	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 disabled on management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be disabled only on a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment (i.e `real-bmh` for capm3 )

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.

Closes #3547 (closed)

Edited Feb 13, 2026 by Alexandre Seitz

CI: regression in "add a new dynamic disabled unit option 🔴"

What does this MR do and why?

Related reference(s)

Test coverage

we have tested the following cases:

CI configuration

Global config for deployment pipelines

Merge request reports