Set label on sylva components namespaces (!7558) · Merge requests · Sylva-projects / sylva-core

The aim of this MR is to made a first step to limit our monitoring system and allow only sylva components to interact with it. In order to achive it we have to indicate which namespaces are in our interest by having a specific label and change the prometheus configuration to rely on it. We are using multiple ways to create namespaces, into this MR I was trying to follow each method:

units based on kustomization ( eg namespace-defs, unit-x-init) and helmrelease where the namespace is created as a part of the chart, put the label by adding commonMetadata.labels
kyverno policy used to cover those namespaces created via operator/subcharts and units based on helmreleases ( having install.createNamespace: true will rely on helm controller to create the namespace).
kyverno unit should be covered by the second method, but kyverno policy is not able to handle own resources, so in order to overcome it I've introduced a new unit called kyverno-init which is responsible to create the namespace.

Closes: #3921 (closed)

What does this MR do and why?

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

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 May 08, 2026 by Bogdan Antohe

Set label on sylva components namespaces

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports