-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Avoid large number of connection error traces in kubeadm controlplane controller #12106
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
🌱 Avoid large number of connection error traces in kubeadm controlplane controller #12106
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.
left nits, otherwise LGTM
@dmvolod Thank you, very nice catch! Change is in general fine, but please rebase on top of main we now basically have this log statement twice and we should adjust both of them |
c701a6d
to
51de879
Compare
Yes, sure, fixed. Please review |
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
LGTM label has been added. Git tree hash: 228873c227f0788932426efda8daa498b3edec35
|
fbcd203
to
a377e26
Compare
Thx! /lgtm |
LGTM label has been added. Git tree hash: a02300f1778f0257653f0120b16fe1fa3af092ac
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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:
This small fix removes large number of stack traces of the workload cluster connection error while it's not ready. The logs spams with predictable stack trace on each reconcile loop with full stack trace instead connection is not ready info.
Another fix can be implemented with validation
controlPlane.Cluster.Status.InfrastructureReady
before connection to avoid connection problems and large number of noisy stack traces.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 #
/area control-plane