Trigger additional reconciliation when one-shot units are active (!7965) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR introduces a mechanism to trigger an additional reconciliation of Kustomization/sylva-units-status when a one-shot unit is enabled and not yet marked as done.

When such a unit is active in the current run, the annotation sylva-units.sylva-project.org/additional-reconciliation-requested is added to Kustomization/sylva-units-status. This triggers an upgrade, which disables the unit and causes the HelmRelease controller to prune it right away, ensuring one-shot units are cleaned up as soon as they complete.

The annotation is set when $current_one_shot_units is not empty, i.e. at least one one-shot unit is active in the current run and not yet tracked as done in the ConfigMap.

Closes #4062 (closed)

Test coverage

A dedicated unit test suite has been added in tests/one-shot-additional-reconciliation_test.yaml, covering the next scenario:

A one-shot unit is enabled and not yet marked as done in ConfigMap/sylva-units-status → annotation must be present with the current release revision.

helm unittest . -f tests/one-shot-additional-reconciliation_test.yaml

### Chart [ sylva-units ] .

 PASS  Validate additional reconciliation annotation for one-shot units tests/one-shot-additional-reconciliation_test.yaml

Charts:      1 passed, 1 total
Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshot:    0 passed, 0 total
Time:        2.195229307s

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 Jul 17, 2026 by Andra-Simona Delicostea

Trigger additional reconciliation when one-shot units are active

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports