os-images-server: clone into workload clusters the os-image-info configmap produced by the chart

Related issue: automatic OS image activation (capm3) (#2014 - closed) This MR was initially submitted as !3695 (merged), which was then reverted in !3935 (merged) because of #2127 (closed).

The issue is solved by sylva-projects/sylva-elements/helm-charts/os-image-server!124 (merged) which this MR integrates.

Closes #2127 (closed)

---

This MR needs to merge after !3668 (merged).

This MR depends on the os-image-server evolution that introduces this output config map: sylva-projects/sylva-elements/helm-charts/os-image-server!109 (merged)

This MR does not change the observable behavior of our system, it is only an small "isofunctional" refactoring as preparation for MRs implementing #2014 (closed).

Today we clone into workload cluster namespaces the os-images-info ConfigMap produced by the os-images-info unit (for images explicitly enabled in sylva_diskimagebuilder_images and os_images).

In the context of #2014 (closed):

• the os-images-info unit will produce metadata information the os-images-info ConfigMap for all images listed in sylva_diskimagebuilder_images and os_images
• the os-image-server unit will serve a subset of those (thanks to the filters introduced by !3693 (merged)) and will produce the OS images information on this subset in its "output configmap"
• so this "output configmap" is the ConfigMap that we need to clone in workload cluster namespaces

What this MR does is change the ConfigMap that is cloned, but until a future MR comes that will pass a restrictive OS image selector, both configmaps will have the same content.

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
🐧	Node OS	ubuntu, suse
🛠️	Deployment Options	light-deploy, dev-sources, ha, misc
🎬	Pipeline Scenarios	Available scenario list and description

• 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu

• 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

• 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

• ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

• ☁️ capd 🚀 rke2 🛠️ light-deploy 🐧 suse

• ☁️ capo 🚀 rke2 🐧 suse

• ☁️ capo 🚀 kadm 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capo 🚀 kadm 🎬 wkld-k8s-upgrade 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 suse

• ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.3.x 🛠️ ha,misc 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🐧 suse

• ☁️ capm3 🚀 kadm 🐧 ubuntu

• ☁️ capm3 🚀 kadm 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 wkld-k8s-upgrade 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 sylva-upgrade-from-1.3.x 🛠️ misc,ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse

Global config for deployment pipelines

• autorun pipelines
• allow failure on pipelines

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.