Extract sylva-release-info workload clusters ConfigMap in a dedicated unit (!9027) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

It does not solve anything, it's just maybe a maintainability improvement.
I prepared this change for a different idea, that is no longer relevant. Still it feels reasonable to decouple this ConfigMap/sylva-release-info from namespace-defs unit, in light of #2588 (closed) (using the helm-passthrough way, ~~with helm.sh/resource-policy: keep to mimic Kustomization prune: false~~).

Test coverage

We can see in https://gitlab.com/sylva-projects/sylva-core/-/jobs/16366348010/artifacts/file/workload-cluster-dump/ConfigMaps.yaml

- apiVersion: v1
  data:
    additional-info: '{"capi-providers":{"bootstrap_provider":"cabpr","infra_provider":"capo"},"cp-node-count":"3","kubernetes-version":{"current":"v1.36.2+rke2r1","target":"v1.36.2+rke2r1"},"md-node-count":"3"}'
    last-update-started: 2026-09-08 13:10:30.646318638 +0000 UTC m=+3541.527135279
    management-info: |
      cluster-namespace: rke2-capo
      cluster-name: wc-2829414685-rke2-capo
    sylva-core-version: 0.0.0-git-fbd0ae28+c7dbeea433fd
  kind: ConfigMap
  metadata:
    annotations:
      helm.sh/resource-policy: keep
      meta.helm.sh/release-name: sylva-release-info
      meta.helm.sh/release-namespace: sylva-system
    creationTimestamp: "2026-09-08T13:03:57Z"
    :
    name: sylva-release-info
    namespace: sylva-system
    :

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 09, 2026 by Bogdan-Adrian Burciu

Extract sylva-release-info workload clusters ConfigMap in a dedicated unit

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports