-
Notifications
You must be signed in to change notification settings - Fork 983
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
Relax PreferNoSchedule Taint #1485
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✔️ Deploy Preview for karpenter-docs-prod canceled. 🔨 Explore the source changes: f6da842 🔍 Inspect the deploy log: https://app.netlify.com/sites/karpenter-docs-prod/deploys/622a31d46559e40008e364c4 |
dewjam
commented
Mar 8, 2022
ellistarn
reviewed
Mar 8, 2022
ellistarn
reviewed
Mar 8, 2022
ellistarn
reviewed
Mar 8, 2022
ellistarn
reviewed
Mar 8, 2022
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.
Nice fix! A couple comments.
Also -- does this require docs updates?
dewjam
force-pushed
the
PreferNoSchedule
branch
from
March 10, 2022 17:13
c8a9ac1
to
f6da842
Compare
ellistarn
approved these changes
Mar 10, 2022
This was referenced Apr 1, 2023
This was referenced Apr 6, 2023
This was referenced Apr 13, 2023
This was referenced Apr 26, 2023
This was referenced Apr 29, 2023
This was referenced May 4, 2023
This was referenced Aug 29, 2023
This was referenced Sep 5, 2023
This was referenced Sep 13, 2023
This was referenced Sep 20, 2023
This was referenced Sep 27, 2023
This was referenced Oct 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Issue, if available:
#1433
2. Description of changes:
When taints with the effect of
PreferNoSchedule
are applied to nodes, the behavior of kube-scheduler is to only schedule pods to said nodes when no other scheduling options exist. Currently, Karpenter treats taints with the effect ofPreferNoSchedule
asNoSchedule
and will not provision a node with thePreferNoSchedule
taint unless the pod tolerates it explicitly.This change adds a blanket
PreferNoSchedule
toleration to pods when no other Provisioners are selectable and after attempting to relax Affinity terms. In short, Provisioners withPreferNoSchedule
taints which would otherwise meet the pods requirements will be used, but only as a last resort.3. How was this change tested?
A test was implemented in the test suite. Additionally, manual tests were executed with a combination of provisioners configured.
Example using a matching provisioner (PreferNoSchedule toleration is not added to pod):
Example where Affinity terms exist and are relaxed which then match a provisioner (PreferNoSchedule toleration is not added to pod):
Example where only matching provisioner has PreferNoSchedule taint (PreferNoSchedule toleration is added to pod):
Example where no provisioners match (PreferNoSchedule toleration is added to pod, but still no provisioners match):
4. Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.