-
-
Notifications
You must be signed in to change notification settings - Fork 101
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] Creating multiple Kubernetes Secrets by list secrets from Vault. #168
Comments
nightguide
changed the title
[Feature] Creating multiple Kunernetes Secrets from list keys from Vault.
[Feature] Creating multiple Kubernetes Secrets from list keys from Vault.
Sep 13, 2022
nightguide
changed the title
[Feature] Creating multiple Kubernetes Secrets from list keys from Vault.
[Feature] Creating multiple Kubernetes Secrets by list keys from Vault.
Sep 13, 2022
nightguide
changed the title
[Feature] Creating multiple Kubernetes Secrets by list keys from Vault.
[Feature] Creating multiple Kubernetes Secrets by list secrets from Vault.
Sep 13, 2022
Hi @nightguide, can you provide more details? I understand that |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Rico!
Your secret operator is cool.
From the Vault documentation:
I see that by path we can get a list of secrets name from the Vault API.
https://www.vaultproject.io/api-docs/secret/kv/kv-v1#list-secrets
But I don't understand, your operator can create multiple kubernetes secrets obtained from the list of Vault secrets?
I want that when creating one VaultSecret resource, I could get a list of name for all secrets and, based on them, create separate native Kubernetes secrets
It is very comfortable. The operator looks in the path where the secrets lie and creates several native Secrets resources.
The text was updated successfully, but these errors were encountered: