[backport-1.6] Preserve SR-IOV CRDs from deletion when upgrading from Sylva 1.4 (!8438) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Sylva 1.6 changes the namespace the `sriov-crd` Helm release is deployed into, from `cattle-sriov-system` to `sylva-system`. (see !4774 (merged) )

Helm-controller handles a release namespace change as an uninstall + reinstall, which deletes the SR-IOV CRDs and cascade-deletes every resorce created by the SR-IOV operator, such as `SriovNetwork` and `SriovNetworkNodePolicy` in the cluster.

This MR adds a new fix unit `sriov-crd-fix-ns`, which `sriov-crd` now depends on. Before `sriov-crd` applies its new release settings, the unit:

Suspends the sriov-crd HelmRelease, so that deleting it does not trigger a Helm uninstall.
Deletes the Helm release storage secrets (owner=helm,name=sriov-crd) in the target cluster.
Re-annotates the CRDs with meta.helm.sh/release-name and meta.helm.sh/release-namespace matching the new release namespace, so the new release can adopt them.
Deletes the HelmRelease, leaving the resources it deployed in place. The sriov-crd unit then recreates it, which also clears the suspend.

With the Helm storage gone, the recreated HelmRelease results in a fresh install rather than an uninstall + reinstall, so the CRDs are never deleted.

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
⚡	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 Jul 30, 2026 by Ishita Mittal

[backport-1.6] Preserve SR-IOV CRDs from deletion when upgrading from Sylva 1.4

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports