-
Notifications
You must be signed in to change notification settings - Fork 39.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
feat: remove suspendedDaemonPods from daemon controller #84323
feat: remove suspendedDaemonPods from daemon controller #84323
Conversation
|
||
switch { | ||
case wantToRun && !shouldSchedule: | ||
// If daemon pod is supposed to run, but can not be scheduled, add to suspended list. | ||
dsc.addSuspendedDaemonPods(node.Name, dsKey) |
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.
[1] wantToRun and shouldScheudle returns the same all the time
5b03dab
to
dc437a7
Compare
/retest |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: draveness, k82cn, kow3ns 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 |
/kind cleanup
/sig scheduling
/sig apps
What this PR does / why we need it:
After #82795 got merged,
nodeShouldRunDaemonPod
always returns the same value inwantToRun
andshouldSchedule
. The original path [1] will not execute anymore, we could remove suspenedDaemonPods from the daemon controller.Which issue(s) this PR fixes:
Part of #82702
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: