-
Notifications
You must be signed in to change notification settings - Fork 91
Allow the timeout of the csi driver to be set #435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Hi @coolstim. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: coolstim, samuelverstraete The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/okay-to-test |
PR needs rebase. 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-sigs/prow repository. |
Original work by @coolstim PR kubernetes-sigs#435
Is this a bug fix or adding new feature?
This allows the configuration of a previously hard coded setting that controls the timeout of call to the csi driver.
#433
What is this PR about? / Why do we need it?
AWS had an issue taking the provisioning of file systems longer than the 5m default. Now this setting is configurable.
What testing is done?
Deployment with a timeout of 15m during the time that provisioning was taking longer than 5min.