baremetal: allow the use of OS images from previous Sylva versions (!6005) · Merge requests · Sylva-projects / sylva-core

Closes #1942 (closed)

This MR implements the design described in this comment of #1942 (closed).

💡 This MR was carefully crafted as multiple independent commits, and is really meant to be reviewed one commit at a time (in particular because some cleanups were done before the changes, in separate commits). 💡

The result of this MR can be seen at https://gitlab.com/sylva-projects/sylva-core/-/jobs/12075335412/artifacts/browse/management-cluster-dump/os-images/ : there are multiple os-image Deployments and Ingresses to serve both the current OS images and the old ones (https://gitlab.com/sylva-projects/sylva-core/-/jobs/12075335412/artifacts/external_file/management-cluster-dump/Ingresses.summary.txt)

This MR depends on sylva-projects/sylva-elements/helm-charts/sylva-library!134 (merged)

Testing

In https://gitlab.com/sylva-projects/sylva-core/-/jobs/12080044431 we can see that this works as intended:

https://gitlab.com/sylva-projects/sylva-core/-/jobs/12080044431/artifacts/browse/management-cluster-dump/os-images/ show the different pod serving the different images
https://gitlab.com/sylva-projects/sylva-core/-/jobs/12080044431/artifacts/external_file/management-cluster-dump/Ingresses.summary.txt
in https://gitlab.com/sylva-projects/sylva-core/-/jobs/12080044431/artifacts/file/management-cluster-dump/Ingresses.yaml, we can see that the path of the Ingresses is like it was before this MR ; it has the diskimage-builder tag in it and is hence free from collisions ; this was already the case before this MR, I'm mentioning it to show that the image will be available for workload clusters

CI testing:

because it does not seem wise to have all CI runs download all those sylva (n-1) and sylva (n-2) OS images, I'm not changing the default settings to serve by default old Sylva images
I propose to rely on #3026 to have CI testing of this feature

Documentation

I've opened #3157 to track the need to provide documentation for this feature.

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

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 Nov 17, 2025 by Thomas Morin

baremetal: allow the use of OS images from previous Sylva versions

Testing

Documentation

CI configuration

Global config for deployment pipelines

Merge request reports