You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
kubernetes: pin the RetryOnFailure strategy on the Proxmox csi release #4731
packages/apps/kubernetes/templates/helmreleases/csi-proxmox.yaml sets strategy.name: RetryOnFailure on install and upgrade, like csi.yaml and cilium.yaml, but only the KubeVirt pair is pinned (cilium_install_retry_test.yaml, csi_install_retry_test.yaml). Nothing reads the Proxmox one today, because the e2e HelmRelease guard runs only on the KubeVirt substrate. So this is a gap to close before the Proxmox suite starts reusing that guard, not a live defect. A case in substrate_proxmox_addons_test.yaml asserting the strategy on both actions is enough.
Fix in #4969: the mirror test csi_proxmox_install_retry_test.yaml pins RetryOnFailure on both actions of the Proxmox csi release, and the guard comment that pointed at the gap is updated. No template change.
Activity
themoriarti commentedon Oct 19, 2026
Fix in #4969: the mirror test
csi_proxmox_install_retry_test.yamlpinsRetryOnFailureon both actions of the Proxmox csi release, and the guard comment that pointed at the gap is updated. No template change.themoriarti commentedon Oct 28, 2026
Thanks Aleksei Sviridkin (@lexfrei)
test(kubernetes): pin RetryOnFailure on the Proxmox csi release (cozy…
test(kubernetes): pin RetryOnFailure on the Proxmox csi release