fix os-images-info regression, make it run quickly again in more scenarios (!6472) · Merge requests · Sylva-projects / sylva-core

With this MR we ensure that the os-images-info Job will not uselessly process OS images of older Sylva releases.

Reminder:

in !6005 (merged) we introduced the ability for os-image-server unit to serve OS images for baremetal clusters, including for older version of Sylva
these images are only used by clusters using a different version of Sylva, and hence are never candidate for being used by the current cluster (the one for which sylva-units is being rendered)
- (having in mind that the images candidate for selection for the current cluster is controlled via cluster.os_image_selector_autoselect_registries)
having os-images-info process these images is hence absolutely useless in these context:
- context of a mgmt cluster not serving images for baremetal clusters (os-image-server unit not enabled)
- context of a workload cluster (which never have the os-image-server unit enabled)

What this MR does is:

introduce means to filter
when os-image-server unit is not enabled, process only the desired images (relying on cluster.os_image_selector_autoselect_registries)
when os-image-server unit is enabled, do as before this MR (".*" as the regex filter)

Result: we avoid having os-images-info uselessly take 3x the time it was taking before, for many cases (in particular all workload clusters, and capo mgmt cluster)

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 Dec 19, 2025 by Thomas Morin

fix os-images-info regression, make it run quickly again in more scenarios

CI configuration

Global config for deployment pipelines

Merge request reports