Skip to content
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 requirement keys of KWOK instance offerings to well-known labels #2053

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

alec-rabold
Copy link
Contributor

Description

Adds the keys of all requirements for each instance-type offering to the list of Well Known Labels.

This makes it easier to run simulations with non-KWOK NodePools (e.g. using KWOK to simulate how Karpenter would autoscale under certain circumstances in an AWS environment).

Issue: #2045

How was this change tested?

Tested by running locally against a KWOK all-in-one environment (pod).


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Mar 5, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alec-rabold
Once this PR has been reviewed and has the lgtm label, please assign gjtempleton for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 5, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @alec-rabold. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 5, 2025
@coveralls
Copy link

coveralls commented Mar 5, 2025

Pull Request Test Coverage Report for Build 13681049236

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 81.727%

Totals Coverage Status
Change from base Build 13666170746: 0.0%
Covered Lines: 9491
Relevant Lines: 11613

💛 - Coveralls

@@ -169,6 +176,12 @@ func newInstanceType(options InstanceTypeOptions) *cloudprovider.InstanceType {
return req.Values
})))

for _, offering := range options.Offerings {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not just offering requirements, right? It's also the instance type requirements in general? I think we need both

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I'm familiar enough to fully follow; just pushed a commit now to add requirements from both [KWOK]offering.Requirements and [KWOK]offering.Offering.Requirements:

for _, offering := range options.Offerings {
for _, requirement := range offering.Requirements {
v1.WellKnownLabels = v1.WellKnownLabels.Insert(requirement.Key)
}
for _, requirement := range offering.Offering.Requirements {
v1.WellKnownLabels = v1.WellKnownLabels.Insert(requirement.Key)
}
}

Is this what you mean or something else?

@@ -211,6 +211,11 @@ func addInstanceLabels(labels map[string]string, instanceType *cloudprovider.Ins
ret[r.Key] = r.Values()[0]
}
}
for _, r := range offering.Requirements {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this bit means we can drop some of the static things that we are setting around zone and capacity type below

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, removed the explicit zone/capacity-type in ee215df

@@ -139,6 +139,13 @@ func setDefaultOptions(opts InstanceTypeOptions) InstanceTypeOptions {
v1alpha1.InstanceCPULabelKey: cpu,
v1alpha1.InstanceMemoryLabelKey: memory,
}
for _, offering := range opts.Offerings {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little confused by this update -- what is this trying to achieve?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I originally thought this was needed to get the labels added onto the resulting Node but looks like that's not correct - removed in ee215df!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants