-
Notifications
You must be signed in to change notification settings - Fork 320
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
[EKS] [request]: enable support for provisioning gp3 volumes #1187
Comments
Hi @iamsudip We just recently released gp3 support in the EBS CSI driver as part of the most recent release https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/CHANGELOG-0.x.md Are you sure you are using the latest version? |
@mikestef9 How shall we upgrade the driver? We are using kubernetes version 1.18 EKS. |
I guess one has to manually install the CSI driver in the cluster, and use the CSI driver to provision gp3 volumes. Described here: https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html It certainly would help if there was a simple way of having this done automatically. |
Any way to support gp3 without using EBS CSI driver? |
Can this please be added to the standard EBS storage class provisioner? I believe a lot of us prefer not to migrate to the CSI driver just for this functionality. |
I'd like to see out-of-the-box
|
Closing as latest release of EBS CSI driver now supports gp3 https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/CHANGELOG-0.x.md#v080 We do not have any plans to backport gp3 support to the deprecated in-tree provisioner. Our focus right now is on getting the EBS CSI driver to 1.0 release in preparation for enabling the CSIMigration flag on EKS clusters. |
@mikestef9 how do I even go about using the EBS CSI driver? Running EKS Kubernetes version |
You can find documentation for using the EBS CSI driver here https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html and more information in the GitHub project https://github.com/kubernetes-sigs/aws-ebs-csi-driver |
@mikestef9 does having to do all this manual work to get the EBS CSI driver up and running kind of defeat the purpose of paying for EKS? I.E. since I don't have the EBS CSI driver setup, what is my EKS cluster using currently? |
We are very close to launching EKS add-ons support for the EBS CSI driver, you can follow this issue for progress #247. This will provide a one click installation experience for the EBS CSI driver. |
@mikestef9 thanks for the information and link to the issue. I do wonder though, why is EBS CSI driver a plugin and opt-in? Shouldn't it just replace the current driver starting at maybe Kubernetes version |
I am also curious, why CSI driver isn't the default in AWS EKS. Also, more curious why gp3 isn't the default choice in EKS. |
Hi @mikestef9 I'm currently using CSI driver to apply |
Is there any impact of modifying the |
I would like to know this as well. All our prometheus volumes have been created as gp2 and just updating the helm values to gp3 the provisioning of the pvc failed. So I thought, I could just provision as gp2 and then update on the AWS console... |
I think you should be fine making this change in the AWS console in EBS volumes, but of course it would NOT persist if the volumes are delete and re-created by Kubernetes or future new Kubernetes volumes will still default to gp2. |
Can you give a quick and dirty cliff notes version how you go this working? I am using the opt-in add-on
Don't see |
Hi @nodesocket , you should manually install CSI driver into EKS cluster by following above mentioned documents like https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html or https://github.com/kubernetes-sigs/aws-ebs-csi-driver . |
Hi @winter7 , @nodesocket , Experimented with upgrading the type from |
Community Note
Tell us about your request
Add support for provisioning gp3 volume: https://github.com/kubernetes-sigs/aws-ebs-csi-driver
Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I have provisioned "gp3" storageclass and tried adding a pvc/pv. But it failed with
Warning ProvisioningFailed 9s (x5 over 59s) persistentvolume-controller Failed to provision volume with StorageClass "gp3": invalid AWS VolumeType "gp3"
. The underlying volume-provisioner managed by controlplane needs an upgrade.Are you currently working around this issue?
Still using
gp2
The text was updated successfully, but these errors were encountered: