Repository navigation

Commit 866588f

myasnikovdaniil

committed

fix(kubernetes): add spec.timeout to tenant CSI HelmRelease

Aligns kubevirt-csi-node HR with every other tenant addon HR in packages/apps/kubernetes/templates/helmreleases/ (cilium, coredns, ingress-nginx, etc.) — all set timeout: 10m, csi.yaml was the only exception. 9f9d8f8 ("Allign timeouts for HelmReleases") missed it. Symptom: e2e NFS test (hack/e2e-apps/run-kubernetes.sh) times out waiting for nfs-test-pod to reach Succeeded. Cozyreport events show the tenant csi HR running Install -> Uninstall -> Install remediation cycles. With install.remediation.retries: -1 and the default 5m Helm timeout, kstatus marks the kubevirt-csi-node DaemonSet 'InProgress' past 5m on a slow tenant control-plane bringup (Kamaji APIs flapping, VM image pulls), helm-controller times out, the remediation uninstalls the DaemonSet, then reinstalls. Any volume mount in flight at that moment is wedged. Observed on PR #2619 CI run 26142986969: csi HR remediation at ~07:07 happened ~10 min into the nfs-test-pod wait, killing the mount and timing out the pod-Succeeded condition. 10m matches the surrounding HRs and gives the DaemonSet headroom without changing remediation semantics on truly-broken installs. Signed-off-by: Myasnikov Daniil <[email protected]>

1 parent ef07600 commit 866588fCopy full SHA for 866588f

1 file changed

packages/apps/kubernetes/templates/helmreleases
- csi.yaml

`‎packages/apps/kubernetes/templates/helmreleases/csi.yaml‎`

-Original file line number
+Diff line change
     sharding.fluxcd.io/key: tenants
 spec:
   interval: 5m
 +  timeout: 10m
   releaseName: csi
   chartRef:
     kind: ExternalArtifact

Comments

(0)