-
Notifications
You must be signed in to change notification settings - Fork 1.5k
CORS-4212: AWS: Add the ability to configure throughput on GP3 volumes #9945
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -71,6 +71,9 @@ func (a *MachinePool) Set(required *MachinePool) { | |
| if required.EC2RootVolume.IOPS != 0 { | ||
| a.EC2RootVolume.IOPS = required.EC2RootVolume.IOPS | ||
| } | ||
| if required.EC2RootVolume.Throughput != 0 { | ||
| a.EC2RootVolume.Throughput = required.EC2RootVolume.Throughput | ||
| } | ||
| if required.EC2RootVolume.Size != 0 { | ||
| a.EC2RootVolume.Size = required.EC2RootVolume.Size | ||
| } | ||
|
|
@@ -107,6 +110,13 @@ type EC2RootVolume struct { | |
| // +optional | ||
| IOPS int `json:"iops"` | ||
|
|
||
| // Throughput to provision in MiB/s supported for the volume type. This | ||
| // is currently only applicable to volumes of type gp3. | ||
| // | ||
| // +kubebuilder:validation:Minimum=0 | ||
jhixson74 marked this conversation as resolved.
Show resolved
Hide resolved
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The minimum is 125 in the API, why would it be different here?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks, it will be addressed in #10132
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I based this work directly off of how IOPS was implemented. IOPS makes all the same assumptions and works the same way as Throughput. So I (wrongly) assumed if everyone was okay with how IOPS was implemented, then it would be okay for Throughput.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| // +optional | ||
| Throughput int64 `json:"throughput"` | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Needs to be a pointer so that you can detect between someone trying to explicitly set
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks Joel, I opened #10132 to address this. |
||
|
|
||
| // Size defines the size of the volume in gibibytes (GiB). | ||
| // | ||
| // +kubebuilder:validation:Minimum=0 | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.