-
Notifications
You must be signed in to change notification settings - Fork 14
Description
Is your feature request related to a problem? Please describe.
I am creating my secret with all environment variables (used in the secret.existingSecret value) with Secret provider class for Azure Key vaults, which requires an additional volume in the deployment with a specific path. I am using the version 0.4.0 of this chart, where I can not define such volume: therefore the secret provider class cannot create the corresponding secret.
Describe the solution you'd like
I would need new values that allow to create additional volumes and their mounts like this:
volumes: []
# - name: my_volume
# secret:
# secretName: my_secret
# optional: false
volumeMounts: []
# - name: mounted_secret
# mountPath: "/etc/mounted_secret"
# readOnly: trueDescribe alternatives you've considered
At the moment I am creating the secret manually locally and I apply it: it works, but it is quite cumbersome.
Additional context
I noticed another issue which would benefit by having the chance to define additional volumes and their mounts: #12