Introduce nmstate-resources chart (!6151) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Intorduces a new unit nmstate-resources based on a custom helmchart allowing the user to create NodeNetworkConfigurationPolicies based on a set of predefined formatted values:

nmstate_policies:
  bridge-on-vlan:
    nodeSelector:
      beta.kubernetes.io/os: linux
    maxUnavailable: 1
    routes:
      - destination: 2.2.2.0/30
        metric: 150
        next-hop-address: 192.168.10.1
        next-hop-interface: bond0.200
        table-id: 254
    interfaces:
      bridges:
        br10:
          description: Linux bridge with bond0.200 as a port
          ports:
            - name: bond0.200
      vlans:
        bond0.200:
          interface: bond0
          id: 200

The current version of the chart is limited to only create bridges, vlans and static routes, whithout ipv4 configurations. It can be evolved in the future to support other types of configurations as needed. Values are enforced by the schema. A verification is done so that the bridges/vlans do not bind to any interface used by the primary network to avoid connectivity issues to the cluster.

Depends on

sylva-projects/sylva-elements/helm-charts/nmstate-resources!1 (merged)

sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!315 (merged)

sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!430 (merged)

~~sylva-projects/sylva-elements/helm-charts/sylva-capi-cluster!1013 (merged)~~

Closes #3021 (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	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	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

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 Jun 08, 2026 by Cristian Manda

Introduce nmstate-resources chart

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports