-
Notifications
You must be signed in to change notification settings - Fork 551
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
Remove operatorgroup queueinformer #2753
Remove operatorgroup queueinformer #2753
Conversation
/lgtm |
The commit message is a bit off eh? We should probably just mention that we no longer:
|
Yeah I think it's probably overly-verbose. I will fix it up. |
/approve |
/hold Commit has @exdx's signature as its header. |
af29d9c
to
e032d48
Compare
Fixed! Sorry about that. /hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene, exdx, timflannagan 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 |
Removes the unneccesary operatorgroup queueinformer, since only an operatorgroup lister is needed. Also ensures that the syncResolvingNamespace function is no longer triggered by operatorgroup events. Signed-off-by: Daniel Sover <[email protected]>
/lgtm |
Description of the change:
An operatorgroup queueinformer was introduced in #2728.
The operatorgroup syncer was calling the syncResolvingNamespace
function, which expects a namespace object as an argument, with an
operatorgroup instead. This led to casting errors.
Since there is no need for an operatorgroup queueinformer, only a lister, the queueinformer can be removed entirely.
Motivation for the change:
Downstream bug
Reviewer Checklist
/doc
[FLAKE]
are truly flaky[FLAKE]
tag are no longer flaky