e2e: update and fix vSphere CSI driver deployment#2164
Merged
anmazzotti merged 1 commit intomainfrom Feb 27, 2026
Merged
Conversation
Signed-off-by: Andrea Mazzotti <andrea.mazzotti@suse.com>
alexander-demicev
approved these changes
Feb 27, 2026
salasberryfin
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR fixes the deployment of CSI.
This is one of the findings from Fleet verification: #2154
The CSI bundle never deploys correctly.
From fleet-agent logs downstream:
{"level":"info","ts":"2026-02-26T14:54:02Z","logger":"bundledeployment.update-status","msg":"Status not ready according to nonModified and nonReady","controller":"bundledeployment","controllerGroup":"fleet.cattle.io","controllerKind":"BundleDeployment","BundleDeployment":{"name":"vsphere-csi","namespace":"cluster-creategitops-s0idyp-cluster-vsphere-rke2-qxg21s-d-4290f"},"namespace":"cluster-creategitops-s0idyp-cluster-vsphere-rke2-qxg21s-d-4290f","name":"vsphere-csi","reconcileID":"2ba61d5f-d85c-4f32-ae8f-bfc3e3d6ef21","nonModified":true,"nonReady":[{"uid":"3a7e0b5c-4e69-41d6-af08-579f59ae02a0","kind":"Deployment","apiVersion":"apps/v1","namespace":"vmware-system-csi","name":"vsphere-csi-controller","summary":{"state":"error","error":true,"message":["ReplicaSet \"vsphere-csi-controller-95c55db4f\" has timed out progressing.","Progress deadline exceeded"]}}]}It looks like the CSI driver manifest uses 3 replicas by default, but the vsphere-csi-controller has a pod anti affinity rule so that it doesn't run twice on the same node, which makes sense.
One solution is to scale down replicas to 1 for this controller, but I think it's best to use default settings and most common scenarios and just deploy 3 control planes then.
The manifest also has been updated for the occasion from https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/manifests/vanilla/vsphere-csi-driver.yaml
Test run: https://github.com/rancher/turtles/actions/runs/22453259876
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist: