Cleanup workaround Kyverno policy for baremetal bond_miimon config (!7584) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR is cleaning up the changes that were introduced by gitlab.com/sylva-projects/sylva-core/-/merge_requests/1730, in order to benefit from the upstream fix that is allowing us to pass network parameters for bond interfaces (see upstream issue)

The dependency on kyverno-policies unit is also being removed from the cluster unit. For CAPM3 scenario, the policies are being created using the kyverno-metal3-policies unit, which is already a dependency for the cluster-bmh unit (on which the cluster unit is depending also).

Closes #2463 (closed)

Test coverage

This was tested on my DEV environment and also in the CI jobs. The output of the secret holding the networkData was the following:

links:
- bond_links:
  - nic1
  - nic2
  bond_miimon: 100 <<<<<<<<<<<<<<
  bond_mode: active-backup
  bond_xmit_hash_policy: layer2
  ethernet_mac_address: "xx:xx:xx:xx:xx:xx"
  id: bond0
  mtu: 1500
  type: bond
- ethernet_mac_address: "xx:xx:xx:xx:xx:xx"
  id: nic1
  mtu: 1500
  type: phy
- ethernet_mac_address: "xx:xx:xx:xx:xx:xx"
  id: nic2
  mtu: 1500
  type: phy
- id: bond0.100
  mtu: 1500
  type: vlan
  vlan_id: 100
  vlan_link: bond0
  vlan_mac_address: "xx:xx:xx:xx:xx:xx"

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 25, 2026 by Dragos Gerea

Cleanup workaround Kyverno policy for baremetal bond_miimon config

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports