This repository has been archived by the owner on Apr 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Allow use of existing secrets #53
Comments
galexrt
added a commit
that referenced
this issue
Oct 10, 2023
Resolves #53 Signed-off-by: Alexander Trost <[email protected]>
galexrt
added a commit
that referenced
this issue
Oct 10, 2023
Resolves #53 Signed-off-by: Alexander Trost <[email protected]>
galexrt
added a commit
that referenced
this issue
Oct 10, 2023
Resolves #53 Signed-off-by: Alexander Trost <[email protected]>
galexrt
added a commit
that referenced
this issue
Oct 10, 2023
Resolves #53 Signed-off-by: Alexander Trost <[email protected]>
galexrt
added a commit
that referenced
this issue
Oct 11, 2023
Resolves #53 Signed-off-by: Alexander Trost <[email protected]>
@jon-rei please try with the latest helm chart version 1.3.0 and let us know if that works for you |
Hi @galexrt, I've just deployed the new version on our cluster and it works, thanks for the quick implementation. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if we could use existing secrets for the exporter.
In our environment we use SealedSecrets to create our secrets. So it would be great if an existing secret could be passed to the helm chart for the
rgw
configuration.The text was updated successfully, but these errors were encountered: