Add the capability to read existing secret for an S3User#107
Merged
Donatien26 merged 4 commits intoSep 23, 2025
Conversation
…et was not deleted & recreated as needed
…te with not owned secret (and fix previous commit)
graindcafe
force-pushed
the
add-read-user-existing-secret
branch
3 times, most recently
from
7f7e84d to
2e076d1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to be able to manage the secret key for an S3 User outside of the S3 Operator.
A new switch (
--read-existing-secret) is introduced in the command line to make the S3 Operator read the secret key from an Kubernetes Secret instead of generating the secret and creation/updating the Kubernetes Secret.