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

rootVolumeType accepts only gp2 or io1 #4256

Closed
int128 opened this issue Jan 11, 2018 · 8 comments
Closed

rootVolumeType accepts only gp2 or io1 #4256

int128 opened this issue Jan 11, 2018 · 8 comments

Comments

@int128
Copy link
Contributor

int128 commented Jan 11, 2018

Instance group spec rootVolumeType seems to accept only gp2 or io1 type.

default:
volumeType = DefaultVolumeType

A SSD volume is best for production but sometimes cheaper standard is convenient for experimental use.
Is there any reason to limit the volume type?

I think it is nice to support following volume types as well:

  • standard
  • st1
  • sc1

Thanks.

int128 added a commit to int128/kops that referenced this issue Jan 13, 2018
int128 added a commit to int128/kops that referenced this issue Jan 14, 2018
int128 added a commit to int128/kops that referenced this issue Jan 14, 2018
@huang-jy
Copy link

See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html

st1 and sc1 cannot be used as boot volumes -- this isn't a restriction by kops, but by AWS.

@tsuna
Copy link
Contributor

tsuna commented Sep 11, 2018

Shouldn't kops reject st1 / sc1 root volumes instead of accepting it and then failing to spin up EC2 instances?

@huang-jy
Copy link

@tsuna possible -- that would however require ongoing maintenance to keeep it in line with AWS

@tsuna
Copy link
Contributor

tsuna commented Sep 11, 2018

Maybe we could have a warning? "Warning: st1 EBS volumes are not known to be usable as root volumes, your instance might not start". Since the list is small and rarely changes, an alternative would be to have a set of known good types, known bad types. If a known bad type is used: error. Otherwise if not-a-known-good-type then issue a warning.

@huang-jy
Copy link

Sounds like a good idea -- perhaps raise a feature request ticket and see if one of the team can pick it up. :)

@ishantanu
Copy link

Folks, I just faced this issue while I was unaware that st1 cannot be used as a boot volume. I believe a warning message would be really nice.

@huang-jy
Copy link

@iamShantanu101 Raise a feature request ticket and link it to this one, that way those who visit this issue because they, like yourself, have encountered the problem, can +1 it

@ishantanu
Copy link

@huang-jy Yes, opening it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants