-
Notifications
You must be signed in to change notification settings - Fork 4k
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 multiple run of informers created in fetcher.go #6157
Conversation
4384e73
to
d54a106
Compare
d54a106
to
96958f8
Compare
go informer.Run(stopCh) | ||
ok := cache.WaitForCacheSync(stopCh, informer.HasSynced) | ||
if !ok { | ||
if !f.Core().V1().LimitRanges().Informer().HasSynced() { |
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.
do we really need this inner if
? It seems to be redundant with cache.WaitForCacheSync(stopCh, informer.HasSynced)
/lgtm |
@laoj2: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kwiesmueller, laoj2, mikutas 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 type of PR is this?
/kind bug
What this PR does / why we need it:
Suppress warn logs
The sharedIndexInformer has started, run more than once is not allowed
appear at every admission-controller startupWhich issue(s) this PR fixes:
Fixes #6156
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: