Add support for nftables Multinetwork Policy (part of k8s Network Plumbing Work Group) for Multus net-attach-def (!7982) · Merge requests · Sylva-projects / sylva-core

Summary:

Kubernetes NetworkPolicy only covers the primary pod interface. Traffic on Multus secondary interfaces (macvlan, ipvlan, bridge, sriov, bond) is unpoliced. This MR adds MultiNetworkPolicy enforcement to cover that gap.

Upstream: https://github.com/k8snetworkplumbingwg/multi-networkpolicy-nftables

Changes:

Sylva Units:
- multi-networkpolicy-crd: installs the CRD
- multi-networkpolicy-nftables: runs the enforcement DaemonSet. depends_on multus.
Upstream is k8snetworkplumbingwg/multi-networkpolicy-nftables but it has no release tags
- ~~Built the image - hosted it in the Sylva ecosystem at.../sandbox-registry/multi-networkpolicy-nftables:0.0.20260511-e141ac5~~
- ~~Injected via postBuild.substitute~~
Hardened for Sylva, not in upstream** (kustomize-units/multi-networkpolicy-nftables/kustomization.yaml).
- privileged: false, dropped to minimal caps (SYS_ADMIN, NET_ADMIN, SYS_PTRACE),
- AppArmor Unconfined + SYS_PTRACE so cross-namespace /proc/<pid>/ns/net works on RKE2,
- /host mount made read-only,
- ClusterRole wildcards replaced with explicit resources/verbs,
- supported plugins (macvlan,ipvlan,bridge,sriov,bond) parameterised.
Disabled by default (workload-cluster.values.yaml): both units enabled: false
Tests: implemented via the new test framework
- test_multi_networkpolicy_crd_exists — To verify mnp crd creation
- test_nftables_daemonset_running — To verify Daemonset
- test_baseline_connectivity — To verify can pods talk over the macvlan secondary interface
- test_policy_enforcement — To verify deny-all-egress blocks iperf traffic

Testing:

CI: all 4 cases pass on capo/rke2/suse, including verified policy enforcement.
Manual: capo + capm3 with the SR-IOV plugin — details in #2234 (closed) comments.

Pre-requisite:

Nodes must have Multus secondary interface.

Co-Author: AI/Claude

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 18, 2026 by Thomas Morin

Add support for nftables Multinetwork Policy (part of k8s Network Plumbing Work Group) for Multus net-attach-def