-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Make gp3 the default EBS volume type #626
Comments
We've discussed this issue, and we want to do some additional validation and performance testing before we make gp3 volumes the default for AMIs. Once we are able to do that, we will add additional details here, including the results. |
Any updates on this topic? Hopefully you've had time to test gp3 volumes by now, and they could be made the default type for new Instances. |
any updates on this topic folks ? |
any updates ? |
|
Any updates? |
I'm on board. Because gp3 can have (sometimes subtle) performance differences, we'll probably make the change starting with a Kubernetes version, like 1.26. I'll put together a PR. |
What would you like to be added:
In December 2020, Amazon EBS announced gp3 volumes, the next generation of general purpose volumes. gp3 volumes are more performant, flexible and have lower costs than gp2 volumes, the current default, and they are available in all commercial and govcloud regions.
We should verify that there are no downsides to this and would not impact any existing customers, but seems like a reasonable change.
Changing it here would make it the default, and we should consider adding a new user variable to set the volume type to simplify it for customers who want to use a different volume type.
And probably update the CFN template.
Why is this needed:
gp3 volumes are the latest generation of EBS volumes and offer benefits over gp2 AMIs.
The text was updated successfully, but these errors were encountered: