-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Feature] Add IO2 volumeType support #7905
Labels
kind/feature
New feature or request
priority/important-longterm
Important over the long term, but may not be currently staffed and/or may require multiple releases
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
i am working on this feature. |
BhowmickSumit
added a commit
to BhowmickSumit/eksctl
that referenced
this issue
Oct 6, 2024
created the pull request - #7989 |
7 tasks
Hi @TiberiuGC , |
dims
pushed a commit
to dims/eksctl
that referenced
this issue
Feb 6, 2025
Signed-off-by: Davanum Srinivas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature
New feature or request
priority/important-longterm
Important over the long term, but may not be currently staffed and/or may require multiple releases
What feature/behavior/change do you want?
I attempted to create a cluster with IO2 volumeType using the following parameters, but the managed nodegroup cloudformation stack fails.
additionalVolumes:
- volumeName: '/dev/sdi' # required
volumeSize: 500
volumeType: 'io2'
volumeIOPS: 3000
After looking through the API, and history of issues, I noticed that only IO1 is supported.
When I adjust the volumeType to 'io1', the managed nodegroup is created successfully.
Why do you want this feature?
Some clusters may want to have IO2 as additional volumes to their managed node groups.
The text was updated successfully, but these errors were encountered: