-
Notifications
You must be signed in to change notification settings - Fork 807
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
Remove premature CreateVolume error if requested IOPS is below minimum #1883
Remove premature CreateVolume error if requested IOPS is below minimum #1883
Conversation
Code Coverage DiffThis PR does not change the code coverage |
f57bf3d
to
190f526
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
190f526
to
7e8ec74
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ConnorJC3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Is this a bug fix or adding new feature?
Bug fix
What is this PR about? / Why do we need it?
EBS CSI Driver will let EC2 CreateVolume enforce minimum IOPS values instead of enforcing the hardcoded minimum limits in cloud.go (Unless
allowAutoIOPSPerGBIncrease
is set).Note: This is a volume-type agnostic version of PR #1879, as requested by EBS CSI Driver team.
Pro:
Con:
infeasable
PVC status is added to CreateVolume similar to how it was added for Update ControllerModifyVolume Status API #4298). This could increase chance of EC2 throttling, but can be solved at the Kubernetes + CSI level viainfeasable
PVC parameter.See #1879
What testing is done?
make test
, Manual testing