Update get_image_refs (!9055) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Improvements:

helm artifact based on ocirepository (sylva-units missing in today inventory)
kind_image Before we tried to guess kind image directly from kind binary, but it doesn't always match the image really used. So now, we save into a file the kind version directly in the bootstrap.sh script. This new file is then saved as gitlab artifact for reuse in other jobs.
make result idempotent as result is a dict with a bunch of lists, the order in each list can varies between each runs. Now we sort all lists before dump, so result is idempotent

Test coverage

If you have a look at job merge-image-refs-report of pipeline #2816849136, you will see both new changes:

helm chart: sylva-units
container image: kindest/node

This code has been also tested with Orange downstream project, we were able to redeploy a complete mgmt and workload cluster from a private registry populated with all oci artifacts listed from this script.

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 07, 2026 by Alexandre Seitz

Update get_image_refs

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports