-
Notifications
You must be signed in to change notification settings - Fork 14
✨ use SecretManager to handle access to cluster secrets #441
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: main
Are you sure you want to change the base?
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
267077b to
a76d5df
Compare
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.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
a76d5df to
598393a
Compare
|
Changed label name and rebased, should be good now. |
598393a to
1661d0a
Compare
Make lint locally and GH workflow did not agree on linting here :( Created #456 to track that inconsistency. |
matthewei
left a comment
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 still need to monitor secret?
|
/lgtm Thanks!
Not sure I fully understand the question, but owning the secret ensures that the controller gets notified when it changes, while this change ensures the relevant (and only relevant) secrets are cached. |
Use the SecretManager from BMO to also handle secrets in IRSO. Instead of holding all cluster secrets in cluster client cache, we only keep the ones that match our labels. This lowers memory consumption but also prevents a risk that the cluster secrets might get dumped. Signed-off-by: Tuomo Tanskanen <[email protected]>
1661d0a to
5418793
Compare
|
/lgtm Thanks! |
What this PR does / why we need it:
Use the SecretManager from BMO to also handle secrets in IRSO. Instead of holding all cluster secrets in cluster client cache, we only keep the ones that match our labels. This lowers memory consumption but also prevents a risk that the cluster secrets might get dumped. This has been adapted from BMO's SecretManager.
Fixes #425
Checklist: