-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Add usage for per-profile node affinity #24914
Add usage for per-profile node affinity #24914
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 45da527 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5faae0990c9933000803d2c8 |
/milestone 1.20 |
/assign |
87d64a9
to
3504b33
Compare
3504b33
to
059c6c8
Compare
/assign @Huang-Wei |
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.
Just one nit. LGTM otherwise.
/hold cancel |
@annajung - is this PR you are referring merged k/k merged? kubernetes/kubernetes#96202. Kindly mention in your comment , thanks. |
/lgtm |
@raghvenders: changing LGTM is restricted to collaborators In response to this:
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/test-infra repository. |
Please leave lgtm for sig-scheduling approver. I'll handle the comments
tomorrow.
…On Mon., Nov. 9, 2020, 7:53 p.m. Kubernetes Prow Robot, < ***@***.***> wrote:
@raghvenders <https://github.com/raghvenders>: changing LGTM is
restricted to collaborators
In response to this
<#24914 (comment)>:
/lgtm
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24914 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ5E6ESZDTFIB6HSEQNFJLSPCFH7ANCNFSM4TL4O7BQ>
.
|
Thanks @alculquicondor.On a note , reviewers or approves can do anyways not me. |
059c6c8
to
4b786a4
Compare
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.
Some feedback. I wasn't clear on why someone might want to configure the NodeAffinity plugin the way that this PR suggests.
recommend to use node labels that have clear correlation with the profile's scheduler name. | ||
|
||
{{< note >}} | ||
The Daemonset controller, which [creates Pods for Daemonsets](/docs/concepts/workloads/controllers/daemonset/#scheduled-by-default-scheduler) |
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.
nit:
The Daemonset controller, which [creates Pods for Daemonsets](/docs/concepts/workloads/controllers/daemonset/#scheduled-by-default-scheduler) | |
The DaemonSet controller, which [creates Pods for DaemonSets](/docs/concepts/workloads/controllers/daemonset/#scheduled-by-default-scheduler) |
AIUI the DaemonSet controller sets a NodeAffinity
on the Pods it creates and otherwise gets out of the way. So is this really about handling Pods with narrow NodeAffinity?
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.
That is correct, but it's generally up to the user to fix narrow affinities. They can do that once they observe the failed scheduling event.
But DaemonSet Pods might be particularly confusing because there's a k8s controller that creates them.
When configuring multiple [scheduling profiles](/docs/reference/scheduling/config/#multiple-profiles), you can associate | ||
a profile with a Node affinity. To do so, add an `addedAffinity` to the args of the [`NodeAffinity` plugin](/docs/reference/scheduling/config/#scheduling-plugins) | ||
in the [scheduler configuration](/docs/reference/scheduling/config/). For example: |
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.
Why might you want to do this?
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.
Added
4b786a4
to
45da527
Compare
/lgtm |
LGTM label has been added. Git tree hash: 7914970c489f6c98f4428dfc3b234cbc06289582
|
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irvifa The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/sig scheduling
Implementation PR: kubernetes/kubernetes#96202
Ref kubernetes/kubernetes#95738