We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
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.
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:
uname -a
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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:
Then look at the logs, you'll see on all 3 instances:
Anything else we need to know?:
Environment:
uname -a
):The text was updated successfully, but these errors were encountered: