Cleaning up stale CnsVolumeOperationRequest instances should only be done on one controller

[sathieu]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:

Cleaning up stale CnsVolumeOperationRequest instances can be a intensive operation on cluster with a lot of CnsVolumeOperationRequest.

Currenlty this goroutine is run on all controllers, i.e 3 instances by default.

What you expected to happen:

Only the controller holding a lease should do this operation.

How to reproduce it (as minimally and precisely as possible):

Run:

kubectl rollout restart -n vsphers-csi deployment vsphere-csi-controller

Then look at the logs, you'll see on all 3 instances:

Cleaning up stale CnsVolumeOperationRequest instances.

Anything else we need to know?:

Environment:

• csi-vsphere version: 3.3.1 vanilla
• vsphere-cloud-controller-manager version: N/1
• Kubernetes version: 1.30.3
• vSphere version: 8.0
• OS (e.g. from /etc/os-release): Debian
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sathieu]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sathieu]

/remove-lifecycle rotten