keep is_upgrade stable across additional reconciliations (!8619) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Since !7965 (merged), enabling a one-shot unit makes sylva-units-operator trigger an additional Helm release once sylva-units-status is reconciled. is_upgrade was recomputed on that release, saw a completed installation, and flipped to true in the middle of a fresh deployment.

The sylva-units-status ConfigMap, written at the end of the dependency chain, now records the is_upgrade value used by the release that completed and whether that release requested an additional reconciliation. When the ConfigMap says the last completed release requested a pass and the chart version is unchanged, the current release is that pass (or a retry of it) and the recorded value is reused. In every other case is_upgrade is recomputed from the Kustomization inventory as before.

A ConfigMap is used rather than the Kustomization annotation because a Helm upgrade interrupted after applying the Kustomization loses the annotation, while the ConfigMap is only rewritten once the whole chain reconciles. The chart-version check ensures a new apply.sh deploying another version is never mistaken for a retry.

Closes #4404 (closed)

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	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 Sep 10, 2026 by Dragos Gerea

keep is_upgrade stable across additional reconciliations

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports