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.

Sign up for GitHub

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

Jump to bottom

[Feature] Add IO2 volumeType support #7905

Open
mylesw42 opened this issue Jul 29, 2024 · 2 comments
Open

[Feature] Add IO2 volumeType support #7905

mylesw42 opened this issue Jul 29, 2024 · 2 comments
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

@mylesw42
Copy link

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.
@mylesw42 mylesw42 added the kind/feature New feature or request label Jul 29, 2024
@github-actions GitHub Actions
Copy link
Contributor

Hello mylesw42 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

@github-actions GitHub Actions
Copy link
Contributor

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.

@github-actions github-actions bot added the stale label Aug 29, 2024
@TiberiuGC TiberiuGC added priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases and removed stale labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mylesw42 @TiberiuGC