Skip to content

e2e: update and fix vSphere CSI driver deployment#2164

Merged
anmazzotti merged 1 commit intomainfrom
fix_vsphere_tests
Feb 27, 2026
Merged

e2e: update and fix vSphere CSI driver deployment#2164
anmazzotti merged 1 commit intomainfrom
fix_vsphere_tests

Conversation

@anmazzotti
Copy link
Contributor

@anmazzotti anmazzotti commented Feb 26, 2026

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:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

Signed-off-by: Andrea Mazzotti <andrea.mazzotti@suse.com>
@anmazzotti anmazzotti self-assigned this Feb 26, 2026
@anmazzotti anmazzotti added the area/capv Cluster API Provider vSphere label Feb 26, 2026
@anmazzotti anmazzotti added kind/ci Issues or PRs related to CI workflows and removed needs-kind labels Feb 26, 2026
@anmazzotti anmazzotti moved this to In Progress (8 max) in CAPI / Turtles Feb 26, 2026
@anmazzotti anmazzotti moved this from In Progress (8 max) to Docs/Proposals For Review in CAPI / Turtles Feb 27, 2026
@anmazzotti anmazzotti moved this from Docs/Proposals For Review to PR to be reviewed in CAPI / Turtles Feb 27, 2026
@anmazzotti anmazzotti marked this pull request as ready for review February 27, 2026 07:30
@anmazzotti anmazzotti requested a review from a team as a code owner February 27, 2026 07:30
@anmazzotti anmazzotti enabled auto-merge February 27, 2026 09:14
@anmazzotti anmazzotti merged commit 0b49fde into main Feb 27, 2026
15 of 33 checks passed
@anmazzotti anmazzotti deleted the fix_vsphere_tests branch February 27, 2026 13:35
@github-project-automation github-project-automation bot moved this from PR to be reviewed to Done in CAPI / Turtles Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/capv Cluster API Provider vSphere kind/ci Issues or PRs related to CI workflows

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants