Disable pre upgrade units in dev (!6930) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

On each run of apply.sh, sylva-units-operator waits for the upgrade of its own kustomization as well as flux-system kustomization, this thakes times and slows down the feedback on helm templating errors for example.

This is usually useless in such envs that are following main, since upgrades of such components should happen seamlessly in these envs that are following main (if not, developers may just have to re-run apply.sh on failures).

This MR disables the pre-upgrade units in dev envs, and also reverts the patching of these units (commit 729c1e53) in applys.sh that was only usefull for the transition to sylva 1.6.

On my env, it used to take 57 seconds to apply sylva-units HelmRelease manifests:

2026-02-12T09:22:29Z    DEBUG   Ensuring SylvaUnitsSource
2026-02-12T09:22:29Z    INFO    Applied changes to GitRepository
2026-02-12T09:22:29Z    INFO    Updated flux-system to use new sourceRef
2026-02-12T09:23:12Z    DEBUG   flux-system Kustomization is up-to-date and ready
2026-02-12T09:23:26Z    DEBUG   sylva-units-operator Kustomization is up-to-date and ready
2026-02-12T09:23:26Z    INFO    Applied changes to HelmRelease sylva-system/sylva-units

With proposed change it takes 26 seconds (31 seconds less)

2026-02-12T09:34:36Z    DEBUG   Ensuring SylvaUnitsSource
2026-02-12T09:34:36Z    INFO    Applied changes to GitRepository
2026-02-12T09:34:36Z    DEBUG   No kustomizations found with pre-upgrade label, skipping pre-upgrade sync
2026-02-12T09:35:02Z    INFO    Applied changes to HelmRelease sylva-system/sylva-units

Test coverage

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
🏗️	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.

Edited Jun 02, 2026 by Thomas Morin

Disable pre upgrade units in dev

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports