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.
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.