oracle / oracle/oci-cloud-controller-manager
Add support for Performance based auto-tune block volumes
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
We would like to be able to define a storage class with performance based auto-tune parameters. For example, be able to define a ultra high performance block volume with auto-tune parameters of a min of 30 VPU and 120 VPU.
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: oci-higher-performance-noatime
parameters:
attachment-type: paravirtualized
auto-tune-min: "30"
auto-tune-max: "120"
provisioner: blockvolume.csi.oraclecloud.com
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; start by tracing how the Kubernetes CSI provisioner reads StorageClass parameters for block volumes. Use the supplied StorageClass as the input case and confirm that auto-tune-min and auto-tune-max are accepted and applied as the requested performance range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100