Add issuer in the vault's kubernetes config #19808
Merged
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.
/cc @openshift/openshift-team-developer-productivity-platform-maintainers @alvaroaleman
The
secret-bootstrap
job and thevault-secret-collection-manager
were failing with errorErrors:* claim "iss" is invalid
That started to happen after we upgrade the app.ci cluster. After some investigation and advice by vault issue hashicorp/vault-k8s#14 which led me to external-secrets/kubernetes-external-secrets#721 it seems that disabling the
iss
validation in Kubernetes config solved the issue.@alvaroaleman I am not sure if this is the best way to fix this or we need to add a specific issuer in the config and keep the validation. Can you check?
Signed-off-by: Nikolaos Moraitis [email protected]