-
Notifications
You must be signed in to change notification settings - Fork 1.5k
monitor secret resources ony if necessary #2550
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
Conversation
* removes the default watch for all secret resources in the cluster * create watch for specific secret resource if required for OIDC feature * do not configure rbac permissions for secrets by default * provide helm chart configuration options for specific secret resources
Skipping CI for Draft Pull Request. |
Codecov Report
@@ Coverage Diff @@
## main #2550 +/- ##
==========================================
+ Coverage 53.52% 53.70% +0.17%
==========================================
Files 142 144 +2
Lines 8039 8121 +82
==========================================
+ Hits 4303 4361 +58
- Misses 3414 3438 +24
Partials 322 322
Continue to review full report at Codecov.
|
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: kishorj, M00nF1sh 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 |
* monitor secret resources ony if necessary * removes the default watch for all secret resources in the cluster * create watch for specific secret resource if required for OIDC feature * do not configure rbac permissions for secrets by default * provide helm chart configuration options for specific secret resources * remove option to configure specific secret names * use channel for secrets event
Issue
Fixes: #2159
Description
The controller until this fix required access to all secret resources in the cluster. The secret resources were used for OIDC feature for the clientID and clientSecret stored in the secret resource. The controller setup a watch during initialization in order to reconcile the affected ingress group and and depending on the number of secrets in the cluster, there is a potential for slower initialization and increased resource usage.
The secret access is not required when OIDC feature is not in use. Furthermore, we can restrict the controller to specific secrets required for the OIDC feature. This PR contains the following changes:
Tests
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯