You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 KV secret engine can have nested paths. An example of what you actually want would be useful.
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: