Make get_image_refs.py retrieve the OCI artifacts needed by a workload cluster (!7853) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

With this MR, the merge_image_refs.py script produces a file with the oci_artifacts element filled when executed on a workload cluster. The OCI artifacts put in the file are those necessary for the deployment of the workload cluster, i.e. they are found in the resources in the namespace of the workload cluster on the management cluster.

The script is compatible with the way it is called in CI in the sense that the output format is unchanged, and that the script can be called with the kubeconfig of the workload cluster (the namespace of the cluster is deduced automatically from the deployed clusters by matching the cluster IP address and port).

This MR is based on the modifications for !7810 (merged), which must be merged first.

It also reuses a part of !7565 to include the sylva-units artifact (chart or chartRef in the helmreleases), with an adaptation necessary for the case where it is called for a workload cluster.

Closes #4044 (closed)

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 Jul 23, 2026 by Thomas Morin

Make get_image_refs.py retrieve the OCI artifacts needed by a workload cluster

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports