Need to add parameters to specify hyper disk specification (IOPS / throughput)
Maintainers usually reply within 1 day
@siddhartha-quad is already working on this.
Since Sep 25, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- gcp, go
- Domain
- cloud, infrastructure
Research direction
Look for the blueprint configuration files related to worker node disk specification, likely in a directory like 'blueprints' or 'modules'. Search for existing disk configuration code to understand the structure. The change involves adding fields for IOPS and throughput to the hyper disk spec and ensuring they are passed to the GCP provider. Check for any validation or tests for disk configuration to update.
Written by the indexing model from the issue text.
Description
For worker nodes we want to use hyper-disks, but specify IOPS/throughput in our blueprint. Currently I can't change it
- Dominant language
- Go
- Stars
- 366
- Forks
- 329
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 98
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from GoogleCloudPlatform/cluster-toolkit
-
slurm-gcp-v6-nodeset: per-nodeset google_compute_zones data source makes terraform state O(N^2) with many nodesetsPossibly taken @nikosavola claimed this 8 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GoogleCloudPlatform/cluster-toolkit#6432 · 1 assignee ·
Maintainers usually reply within 1 day
-
HTCondor job error when downscalingPossibly taken @siddhartha-quad claimed this 11 days ago. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
GoogleCloudPlatform/cluster-toolkit#6409 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
GKE monitoring component ordering causes persistent Terraform driftMay be free again @danehans claimed this 28 days ago, and no pull request is open. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
GoogleCloudPlatform/cluster-toolkit#6331 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GoogleCloudPlatform/cluster-toolkit#6244 · 3 comments ·
Maintainers usually reply within 1 day
-
Add an agentgateway-based multi-provider AI gateway blueprint for GKEPossibly taken @danehans claimed this 35 days ago. Openquestion
GoogleCloudPlatform/cluster-toolkit#6213 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in GoogleCloudPlatform/cluster-toolkit
Similar issues
-
documentation hacktoberfest priority: low skill: good first issue status: ready for dev
Difficulty 2/5 Half a day Newbie friendliness 85/100
hyperledger-labs/fabric-smart-client#2142 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
numberly/vault-db-injector#107 ·
Maintainers usually reply within 1 day
-
area/import kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[DOC] Wrong sg_egress_ports range in the Terraform Databricks Guide for AWS Hub & Spoke with Network FirewallPossibly taken @akhil9tiet claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
databricks/terraform-provider-databricks#6080 · 1 comment ·
Maintainers usually reply within 3 days
-
spqr-coordinator usage shows 'run --config', but 'run' is not a subcommand (unknown command "run")Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pg-sharding/spqr#3092 · 1 comment ·
Maintainers usually reply within 1 day