Provisioner, attacher,... too long to respond after a crash

[jacen57]

/kind bug

What happened:
When a vsphere-csi-driver pod container restarts due to an issue, a timeout of 300 seconds is applied.
However, by default, this timeout is set to 10 seconds. Why was this timer set to 300 seconds?
helm-chart or vanilla

This can result in a very long duration for creating or modifying PVC (up to 5 minutes).

Environment:

• csi-vsphere version: 3.2.3 and higher
• Kubernetes version: 1.27.7

[chethanv28]

@jacen57 The timeout value is set to accommodate VMware's storage back-end taking some time to provision volumes. The timeout 300 seconds is not related to provisioner's restart.

You may be observing a delay during restart (up to 120s) due to the leader election delay - https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/manifests/vanilla/vsphere-csi-driver.yaml#L253

[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