-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix: Health check from lister not apiserver #11375
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.
See discussions in #11374
Signed-off-by: weidongcai <cwdsuzhou@gmail.com>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
Bump |
Since we have disscussed #11374, can we work on this PR now? |
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 am ok with this change. Let's watch for any issues once merged/released
Signed-off-by: weidongcai <cwdsuzhou@gmail.com>
@cwdsuzhou When you tested this, were you able to successfully execute line 37 while catching a Workflow that hadn't been reconciled yet? We noticed a panic occurring on this line, when the |
Signed-off-by: weidongcai <cwdsuzhou@gmail.com> Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com>
Fixes #11374
Motivation
Reduce the
List
check from controller. IMO, it is not reasonable to list from apiserver for health check. Informer is not so reliable and if informer is not healthy, the controller may exit or resync from apiserver.Modifications
Change the health check logic from apiserver to the local cache
Verification