-
Notifications
You must be signed in to change notification settings - Fork 4.2k
add n4d pricing #8657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
add n4d pricing #8657
Conversation
Welcome @mariafromano-25! |
Hi @mariafromano-25. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions 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. |
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/release-note-edit
|
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is n4d pricing not appropriate for inclusion in the customCpuPricePerHour
, customMemoryPricePerHourPerGb
, and customPreemptibleDiscount
categories?
cc @towca
@x13n your insight would be super helpful! Thank you :) |
Well, it depends. Does n4d support custom machine types? |
#8657 (comment) Yes, N4D does support custom machine types |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adds pricing for n4d machine shapes
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: