Add Z4D machine family pricing to GCE cloud provider#9791
Add Z4D machine family pricing to GCE cloud provider#9791mariafromano-25 wants to merge 5 commits into
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
This issue is currently awaiting triage. If SIG Autoscaling contributors determines this is a relevant issue, they will accept it by applying the The DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/retest-required |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mariafromano-25 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest |
|
@mariafromano-25: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds pricing information for the new Z4D machine family to the GCE cloud provider in the Cluster Autoscaler. This ensures the autoscaler can accurately calculate costs and make price-aware scaling and auto-provisioning decisions for Z4D node pools.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
The prices introduced here (vCPU: $0.00875, RAM: $0.01) are the confirmed launch rates. Because the billing SKUs are currently in a pre-release state in the backend and returning dummy values, these hardcoded prices act as a realistic placeholder to prevent the autoscaler from miscalculating costs. An internal tracking bug (b/521945608) has been filed to remove these hardcoded overrides once the real SKUs are fully finalized after GA.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: