-
Notifications
You must be signed in to change notification settings - Fork 151
NO-JIRA: secretannotator: Only pass clients to Reconciler, remove use of non-caching client #865
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
base: master
Are you sure you want to change the base?
Conversation
@stephenfin: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stephenfin The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Stephen Finucane <[email protected]>
c5f6a02
to
02ba77d
Compare
This will allow us to use this caching client shortly. Signed-off-by: Stephen Finucane <[email protected]>
This was first introduced in commit 48d6ccc as a resolution to OCPBUGS-16313 [1][2], which was itself introduced by the removal of configmaps read access from the cluster role used by CCO. However, non-caching clients are expensive and with the change introduced in the previous commit, which restricted caching to specific config maps, plus the existing role allowing access to these config maps, their use should no longer be necessary. [1] openshift#575 [2] https://issues.redhat.com/browse/OCPBUGS-16313 Signed-off-by: Stephen Finucane <[email protected]>
This should have been cleaned up after debugging. Signed-off-by: Stephen Finucane <[email protected]>
/cc @jstuever |
/retest-required |
@stephenfin: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
Per $subject. This makes the clients in use a little more obvious (IMO).