-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 KCP: improve error log on scale up when Machine doesn't have a nodeRef #8564
🌱 KCP: improve error log on scale up when Machine doesn't have a nodeRef #8564
Conversation
Signed-off-by: Stefan Büringer buringerst@vmware.com
cc @rikatz (follow-up to https://kubernetes.slack.com/archives/CKFGK3SSD/p1677254478586479) |
/lgtm Thanks!! Sounds good to me :) |
LGTM label has been added. Git tree hash: a8d5cfe9bbf80f4cdc1f0769eeb278d190a2e625
|
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: vincepri 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 |
/hold cancel |
/area provider/control-plane-kubeadm |
Signed-off-by: Stefan Büringer buringerst@vmware.com
What this PR does / why we need it:
Today KCP produces confusing error messages if it can't scale up the control plane because one of the already existing Machines doesn't have a nodeRef (e.g. because it doesn't have a providerID). This PR improves the error log
Before:
After:
xref: https://kubernetes.slack.com/archives/CKFGK3SSD/p1677254478586479
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #