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

Removed custom label generation. Refactored scheduling logic in preparation for multiple provisioner selection #791

Merged
merged 2 commits into from
Nov 11, 2021

Conversation

ellistarn
Copy link
Contributor

@ellistarn ellistarn commented Nov 10, 2021

1. Issue, if available:

2. Description of changes:

  • Removes the ability for pods to trigger the creation of node labels. Provisioner labels are now required if pods have a corresponding node selector
  • This is in preparation for multiple provisioner selection logic
  • Tweaked hostname topology, which relied upon custom label generation

3. Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: link to issue
  • No

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

@netlify
Copy link

netlify bot commented Nov 10, 2021

✔️ Deploy Preview for karpenter-docs-prod canceled.

🔨 Explore the source changes: e1396c2

🔍 Inspect the deploy log: https://app.netlify.com/sites/karpenter-docs-prod/deploys/618d6560e705f2000943ed54

@ellistarn ellistarn force-pushed the nogen branch 2 times, most recently from 4c1055e to 681b1b2 Compare November 10, 2021 22:49
@JacobGabrielson JacobGabrielson self-requested a review November 10, 2021 23:14
@ellistarn ellistarn changed the title Removed custom label generation. Refactored scheduling logic in preparation for multiple provisioner selection [WIP] Removed custom label generation. Refactored scheduling logic in preparation for multiple provisioner selection Nov 11, 2021
@ellistarn ellistarn force-pushed the nogen branch 2 times, most recently from eb637dd to a095c98 Compare November 11, 2021 01:41
@ellistarn ellistarn changed the title [WIP] Removed custom label generation. Refactored scheduling logic in preparation for multiple provisioner selection Removed custom label generation. Refactored scheduling logic in preparation for multiple provisioner selection Nov 11, 2021
@@ -82,3 +84,56 @@ func (f *Filter) matchesProvisioner(pod *v1.Pod, provisioner *v1alpha5.Provision
}
return fmt.Errorf("matched another provisioner, %s", name)
}

func (f *Filter) hasSupportedSchedulingConstraints(pod *v1.Pod) error {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure it makes sense to introduce new terminology here? Just wondering if Supported might as well be Valid? Or is it actually a new concept? Or maybe call this isValid()?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I can call this Validate()

pkg/controllers/allocation/scheduling/scheduler.go Outdated Show resolved Hide resolved
@ellistarn ellistarn merged commit 5b413e0 into aws:main Nov 11, 2021
@ellistarn ellistarn deleted the nogen branch November 11, 2021 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants