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
Is your feature request related to a problem? Please describe.
Currently the vso crd is mainly used for syncing k8s secrets, but since this is a more k8s native flavored tool in hashicorp's tool box as compared to agent-inject and csi-mounts, would it be in scope to potentially to sync configmaps since configmaps which are almost as sensitive when compared to secrets?
Describe the solution you'd like
if we assume we already store configmaps in vault in a normal kv2 engine the vaultconfigmapspec could look like this:
Is your feature request related to a problem? Please describe.
Currently the vso crd is mainly used for syncing k8s secrets, but since this is a more k8s native flavored tool in hashicorp's tool box as compared to agent-inject and csi-mounts, would it be in scope to potentially to sync configmaps since configmaps which are almost as sensitive when compared to secrets?
Describe the solution you'd like
if we assume we already store configmaps in vault in a normal kv2 engine the vaultconfigmapspec could look like this:
The text was updated successfully, but these errors were encountered: