forked from kubernetes-sigs/karpenter
-
Notifications
You must be signed in to change notification settings - Fork 1
[lifecycle]: skip initialization timeout for nodes running workload pods #52
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
Open
lukeraphael
wants to merge
1
commit into
main
Choose a base branch
from
luke/init-timeout-workload-guard
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Static mirror pods are incorrectly treated as workload
🛑 blocking · rule
high-confidence-regression· confidence 0.88The new workload predicate excludes only DaemonSet pods, terminal pods, and terminating pods. It does not exclude node-owned static/mirror pods, even though this repository's scheduling contract explicitly treats those as non-reschedulable (
pkg/utils/pod/scheduling.go:38-51) and definesIsOwnedByNodeas the static-pod check (pkg/utils/pod/scheduling.go:174-176). A node can therefore have only a kubelet-managed mirror pod while still remaining uninitialized (for example, its bootstrap taint or an extended-resource registration is stuck); this predicate returns true, causing the timeout path at lines 151-154 to requeue forever instead of deleting the stranded NodeClaim/instance. Add!podutils.IsOwnedByNode(pod)(or use the repository's corresponding active/reschedulable classification) and add a mirror-pod regression test. This was validated by tracing the changed predicate todeleteNodeClaimForTimeoutand comparing it with the existing static-pod exclusion used by the node lifecycle scheduling/disruption paths.Suggested fix:
Exclude node-owned static/mirror pods from the predicate (for example, add
&& !podutils.IsOwnedByNode(pod)) and cover a node with only a mirror pod in the initialization-timeout test.Heron review
global-review-orchestrator-guardian· fingerprintfde4ce520718· reply@heron dismiss <reason>to dismiss