We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/kind bug
What happened? Throughput parameter on StorageClass not being implemented for dynamic provisioning.
What you expected to happen? I was using a gp3 EBS type and specified throughput as 250Mb/s, and it came up as 125Mb/s.
gp3
How to reproduce it (as minimally and precisely as possible)? Define a StorageClass as follows:
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: somename parameters: encrypted: "true" iops: "5000" kmsKeyId: "kmskeyId" throughput: "250" provisioner: ebs.csi.aws.com reclaimPolicy: Delete volumeBindingMode: WaitForFirstConsumer
Anything else we need to know?:
Environment
kubectl version
Client Version: v1.24.10-eks-48e63af Kustomize Version: v4.5.4 Server Version: v1.25.8-eks-ec5523e
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. We will fix it. In the meantime, you could use a workaround by specifying the volume type in the parameters.
type: "gp3"
That will provision the correct throughput.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
/kind bug
What happened?
Throughput parameter on StorageClass not being implemented for dynamic provisioning.
What you expected to happen?
I was using a
gp3
EBS type and specified throughput as 250Mb/s, and it came up as 125Mb/s.How to reproduce it (as minimally and precisely as possible)?
Define a StorageClass as follows:
Anything else we need to know?:
Environment
kubectl version
):The text was updated successfully, but these errors were encountered: