Updating IOPS/Throughput for hyperdisk balanced disk
Opened this issue · 2 comments
We can specify provisioned-iops-on-create and provisioned-throughput-on-create in Storage class but that will be only helpful for on create. But we cannot update the values later for the PVs. Using following examples command we can specify IOPS AND Throughput for hyperdisk-balanced for both during create and update. Is there any plan to support following functionality for PersistentVolume using CSI driver. ?
Example
- we can create disk with following command where we can sepcify IOPS and Throughput :
Ref: https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/hyperdisk#gcloud
gcloud compute disks create DISK_NAME
--size=SIZE
--source-snapshot=SNAPSHOT_NAME
--provisioned-throughput=TRHROUGHPUT_LIMIT
--provisioned-iops=IOPS_LIMIT
--type=hyperdisk-balanced
- Update disk IOPS and Throughput using following gcloud command.
Ref : https://cloud.google.com/compute/docs/disks/modify-hyperdisks#gcloud
gcloud compute disks update DISK_NAME
--size=DISK_SIZE
--provisioned-iops=IOPS_LIMIT
--provisioned-throughput=THROUGHPUT_LIMIT
Hi to extend above question.
In k8s we have VolumeAttributesClass to support configuring IOPS and Throughput.
https://kubernetes.io/blog/2023/12/15/kubernetes-1-29-volume-attributes-class/
Is there any plan to support VolumeAttributesClass in GCP CSI driver ?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale