Improve the way we discover chainsaw jobs (!9197) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Following a discussion with @sakuchoudhary98 who hit an issue when testing her MR: !8861 (merged)

Our current implementation was expecting a specific naming convention for chainsaw units. As it was not enforced it was fragile, any chainsaw unit that would not have respected it will lead to a failed test as the framework will try to find a job that doesn't exist.

Current MR change the way we find the job. It will try to retrieve the job of a given kustomization based on labels set by flux:

kustomize.toolkit.fluxcd.io/name={ks_name}
kustomize.toolkit.fluxcd.io/namespace={ks_namespace}

This should be more robust.

Our current implementation of chainsaw, only build one job per unit so I haven't implemented a loop over all possible discovered jobs to keep the code not too complex. A safeguard is added to ensure we only have one job per KS. If this change in the future we could adapt the test.

Fix a minor bug found by claude on the condition to check if log was present.

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 17, 2026 by Loic Nicolle

Improve the way we discover chainsaw jobs

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports