Fix AppRole secret reference #432
Open
Conversation
This file contains 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
|
|
ownercoder
force-pushed
the
fix-approle-secret-reference
branch
from
029ffe1
to
bf4f9f4
Compare
ownercoder
force-pushed
the
fix-approle-secret-reference
branch
from
bf4f9f4
to
66e64a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi!
AppRole has
SecretReffield, which contains name of the k8s secret. When i create AuthStatic in different namespace, i can't get secret, because operator try to get secret from current namespace.For example:
VaultAuth with name
defaultplaced in vault-secrets-operator namespace, also i've created k8s secret in this namespace. When i create AuthStatic withvault-secrets-operator/defaultauth reference in different namespace, i've got an errorFailed to get secretbecause it try to get secret from namespace StaticAuth CR.