vSphere CSI driver makes approximately 55 API calls(every 5 min) to vCenter even when nothing is happening in the cluster

[gnufied]

Using the metric vsphere_request_ops_seconds we can see that, vSphere CSI driver makes approximately 55 API calls to vCenter(every 5 mins, in a cluster with 38 PVs) even if nothing is going on k8s cluster. i.e - no new pods were created that uses a volume, no new volumes were provisioned, no other operation of any kind was initiated by the user.

We also noticed that, between older releases and newer versions number of API calls syncer makes during volume provisioning has almost doubled (but that is a side issue).

I know, we have dangling volume mechanism which periodically polls the backend to ensure we fix up any dangling volumes. But are there any other outliers that can be fixed?

[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