Skip to content
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

Document behavior wrt minimum and maximum iops #582

Merged
merged 1 commit into from
Oct 8, 2020

Conversation

wongma7
Copy link
Contributor

@wongma7 wongma7 commented Oct 7, 2020

Is this a bug fix or adding new feature? fix

What is this PR about? / Why do we need it? unlike in-tree, we error if the iops of a volume is below min or above max. Document it to avoid surprises like #575

What testing is done? N/A

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 7, 2020
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 7, 2020
@coveralls
Copy link

coveralls commented Oct 7, 2020

Pull Request Test Coverage Report for Build 1257

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 81.134%

Totals Coverage Status
Change from base Build 1254: 0.0%
Covered Lines: 1574
Relevant Lines: 1940

💛 - Coveralls

docs/README.md Outdated
@@ -33,7 +33,7 @@ There are several optional parameters that could be passed into `CreateVolumeReq
|-----------------------------|-----------------------------------|----------|---------------------|
| "csi.storage.k8s.io/fsType" | xfs, ext2, ext3, ext4 | ext4 | File system type that will be formatted during volume creation |
| "type" | io1, io2, gp2, sc1, st1,standard | gp2 | EBS volume type |
| "iopsPerGB" | | | I/O operations per second per GiB. Required when io1 or io2 volume type is specified |
| "iopsPerGB" | | | I/O operations per second per GiB. Required when io1 or io2 volume type is specified. If this value multiplied by the size of a requested volume produces a value below the minimum or above the maximum IOPs allowed for the volume type, AWS will return an error and volume creation will fail |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably add a link to the limits: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html

Funnily enough I don't see the minimum IOPS on the chart.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a link.

Yeah it's buried below "io1 and io2 volumes can range in size from 4 GiB to 16 TiB. You can provision from 100 IOPS ..."

@leakingtapan
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 8, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leakingtapan, wongma7

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:
  • OWNERS [leakingtapan,wongma7]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit ee64872 into kubernetes-sigs:master Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants