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

AWS volume type 'standard' missing #365

Closed
MeikelLP opened this issue Sep 9, 2019 · 1 comment · Fixed by #379
Closed

AWS volume type 'standard' missing #365

MeikelLP opened this issue Sep 9, 2019 · 1 comment · Fixed by #379
Milestone
0.5

Comments

@MeikelLP
Copy link

MeikelLP commented Sep 9, 2019

What happened?

In our Rancher fork we wanted to add the volume type standard as it is a valid volume type in AWS (see "Previous Generation Volume Types").

In Rancher we get the message:

Failed to provision volume with StorageClass "ebs-magnetic-purge": invalid AWS VolumeType "standard"

What you expected to happen?

Standard is accepted as volume type.

The array/enum is missing the member standard

Environment

  • Rancher: 2.2.8
  • Kubernetes: 1.14.6
@leakingtapan leakingtapan added this to the 0.5 milestone Sep 9, 2019
@leakingtapan
Copy link
Contributor

Although being undocumented on K8S side: https://kubernetes.io/docs/concepts/storage/storage-classes/#aws-ebs, it is supported by EBS as the link you pasted. Will take a look into this.

@MeikelLP MeikelLP mentioned this issue Sep 12, 2019
Merged
@leakingtapan leakingtapan mentioned this issue Sep 28, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.5
Development

Successfully merging a pull request may close this issue.

Add standard volume type leakingtapan/ebs-csi-driver
2 participants
@leakingtapan @MeikelLP