-
Notifications
You must be signed in to change notification settings - Fork 955
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
feat: add cpu sustained clock speed label to instance metadata #7043
base: main
Are you sure you want to change the base?
feat: add cpu sustained clock speed label to instance metadata #7043
Conversation
✅ Deploy Preview for karpenter-docs-prod ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thanks for your contribution! Running the test workflows. |
Pull Request Test Coverage Report for Build 10949927017Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
@aidan-canva are you able to fix the CI errors? |
This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity. |
@njtran apologies for the delay, I've been on vacation for a period. I've just pushed a fix which should hopefully address the CI failures. Can I kick checks off myself? |
Description
Some workloads are sensitive to variations instance CPU clock speed - either preferring a specific threshold or at least ensuring consistency across replicas. This PR adds the EC2
SustainedClockSpeedInGhz
value as a Karpenter label (karpenter.k8s.aws/instance-cpu-sustained-clock-speed-mhz
) so that workloads can add their preference.The upstream value from the EC2 API is in Ghz and represented as a float (ie 2.4). nodeSelectors only support ints or strings and most use-cases for this will want to leverage the
Gt
orLt
operators to set minimum/maximum values. To make this usable, this implementation converts the Ghz value into Mhz and represents it as an int.How was this change tested?
make test
Does this change impact docs?
Do codegen docs count?
website/content/en/preview/reference/instance-types.md
has been updated to reflect this new instance attribute.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.