Allow to configure maxWaitForUnmountDuration

[shay-berman]

Is this a FEATURE REQUEST?:

/kind feature

What happened:
maxWaitForUnmountDuration is set hardcoded in k8s to 6 minutes so the user cannot change its timing. So a detach of a PVC will always have to wait for 6 minutes.

What you expected to happen:
maxWaitForUnmountDuration should be configurable (probably in the Pod spec or globally).

How to reproduce it (as minimally and precisely as possible):
Stop a pod with PVC, and make the unmount operation to stuck more then 6 minutes. Then a detach will be triggered to this PVC. And there is no way to shrink this 6 minutes.

Anything else we need to know?:
Was discussed as part of #65392

Environment:

• Kubernetes version 1.8+

[neolit123]

/sig storage

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.