-
Notifications
You must be signed in to change notification settings - Fork 28
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
Skip unreachable node during collecting NodeBundles #27
Conversation
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.
LGTM
pkg/manager/manager.go
Outdated
switch cond.Type { | ||
case v1.NodeReady: | ||
if cond.Status != v1.ConditionTrue { | ||
break NODE_LOOP |
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.
maybe continue?
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.
should be continue :P
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.
My bad 🤯 🙇🏾♂️
Fixed!
We currently skip nodes with unavailable network and not ready kubelet. Nodes tainted with `node.kubernetes.io/unschedulable:NoSchedule` are tolerated. Signed-off-by: Weihang Lo <[email protected]>
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.
LGTM
Can we tag a new release for this fix? Thanks |
We currently skip nodes with unavailable network and not ready kubelet.
Nodes tainted with
node.kubernetes.io/unschedulable:NoSchedule
are tolerated.Related issue: harvester/harvester#1524
Any improvement is welcome.