-
Notifications
You must be signed in to change notification settings - Fork 209
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
Feature: Secrets created by ASO should have configurable annotations #1398
Labels
Comments
We're still somewhat interested in this but there hasn't been a lot of user need yet, so going to leave this issue open and see if anybody finds it desirable. |
Still somewhat interested but haven't seen any demand as yet. |
No change from what @theunrepentantgeek said. |
Still no change from this:
|
We're still interested in doing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As originally requested in #1396, @EdYa was looking for a way to allow another namespace access to the secret created by a
PostgreSQLUser
.An example of what this might look like:
We have other fields which are often applicable for secrets as well, such as
KeyVaultToStoreSecrets
. It's possible that it would make sense to move this value into thissecretConfig
at some point in the future as well.The text was updated successfully, but these errors were encountered: