-
Notifications
You must be signed in to change notification settings - Fork 42k
Delete pods assigned to not existing nodes. #73401
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
Delete pods assigned to not existing nodes. #73401
Conversation
|
/ok-to-test |
|
/sig apps |
de5bea5 to
7186d3b
Compare
|
/test pull-kubernetes-node-e2e |
|
/test pull-kubernetes-node-e2e |
|
/test pull-kubernetes-e2e-gce |
|
/assign |
|
|
||
| // getPodsWithoutNode returns list of pods assigned to not existing nodes. | ||
| func getPodsWithoutNode( | ||
| runningNodesList []*v1.Node, nodeToDaemonPods map[string][]*v1.Pod) []string { |
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.
move to a single line :)
|
LGTM ; let's get it merged when CI's happy :) |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: k82cn, krzysztof-jastrzebski The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
isn't this smoothing that the node controller should handle in general? was the problem that they were critical pods? |
|
These pods weren't assigned to nodes by the scheduler yet; they were created with affinity that will only allow them to be placed on a single node—in each case, a node that no longer exists. This happens with pods regardless of whether they're critical or not. We see it happen with pods that need to wait until the node is ready, where the node never became ready before it got deleted. |
BTW, @krzysztof-jastrzebski , would you help to add feature-gate checking there? |
What type of PR is this?
/kind bug
What this PR does / why we need it:
PR adds deleting pods created by DaemonSet assigned to not existing nodes.
Which issue(s) this PR fixes:
Fixes #71349
Does this PR introduce a user-facing change?: