search

kubernetes-sigs / aws-efs-csi-driver

CSI Driver for Amazon EFS https://aws.amazon.com/efs/
Apache License 2.0
711 stars 544 forks source link

Is there a way to specify the `Provisioned Throughput` mode for a PVC? #628

Closed aperepel closed 2 years ago

aperepel commented 2 years ago

I can't seem to find options to configure the performance mode for the claim. Is there a reason or can we add a property to choose between Bursting Throughput (current default) and Provisioned Throughput?

SbgMartin commented 2 years ago

Hi @aperepel ,

the performance mode is defined on AWS EFS itself (bursting, provisioned IOPS) and is used for all volumes using this EFS FileSystem. If you are using bursting mode then you need to have a look at your bursting credits (AWS CloudWatch metrics).

If you need different performance modes available on your K8s cluster using K8s StorageClass with different AWS EFS FileSystems might be a solution for you.

Kind regards Martin

aperepel commented 2 years ago

Thank you, Martin. The use case is a dynamically provisioned EFS file system volume. I don't think I saw any way to specify options there or a generic parameter pass through object in the docs. E.g. there is a lot of flexibility in how one can provision Azure Files (EFS analogue), I hoped to find something similar for the EFS: https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/driver-parameters.md

Or, if I misunderstood something basic and this is possible for a dynamically provisioned volume (vs pre-creating the EFS), let me know, please.

SbgMartin commented 2 years ago

As per my knowledge, only pre-created AWS EFS FileSystems are supported right now. Maybe someone from AWS EFS CSI Driver team could tell about the roadmap towards a dynamic approach.

aperepel commented 2 years ago

Would like to convert this question to a feature request to be able to configure the EFS and provision dynamically, I guess.

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/aws-efs-csi-driver/issues/628#issuecomment-1172934492): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.