-
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: include node list error in KCP and control plane machine conditions #4421
🌱 kcp: include node list error in KCP and control plane machine conditions #4421
Conversation
09c7169
to
35f5617
Compare
LGTM (👋 first time reviewer here) |
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.
I don't have strong opinions here, but I'm not sure that surfacing a plain client-go error could provide actionable informations to the users. however,
/lgtm
@fabriziopandini I'm fine with another solution or just closing the issue without a change. Just thought that was what issue #4234 wanted to change. |
I think it helps add some context to why the operation failed, but agree with @fabriziopandini that I'm not sure it provides actionable information for the user. I'm also not sure that we can provide actionable information for the user (since there are numerous reasons why we might not be able to list the nodes). I'm a +1 on this change since it does provide additional information to the user, and we can always investigate ways to provide more actionable information down the road. |
+1 from me we can always iterate and make the error more actionable if we find a good way to do that. Given the multiple +1s and lgtms |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
What this PR does / why we need it:
Not entirely sure that is what was intended by the issue.
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 #4234