-
Notifications
You must be signed in to change notification settings - Fork 22
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
Gather details for feature requests #239
Comments
Hello there, The HashiCorp's helm-chart in HA mode provides a service, which only points to the "active" vault pod: This is useful for example for the UI, as the service from the operator's vault CR currently directs to inactive pods as well, which cannot be used for UI purposes. If it is supported differently, then I am happy for any hint from your side ;) Thanks in advance and wish you a great day Update/P.S. When I switched to vault version 1.15.0, it appears, that the networking "issue" with the vault UI disappeared. |
Second question/ feature request: When using templates with the vault-agent as in the example in your documentation: template {
contents = <<EOH
{{- with secret "database/creds/readonly" }}
username: {{ .Data.username }}
password: {{ .Data.password }}
{{ end }}
EOH
destination = "/etc/secrets/config"
command = "/bin/sh -c \"kill -HUP $(pidof vault-demo-app) || true\""
} I get the following error:
If I use the path volumeMounts:
- name: agent-secrets
mountPath: /vault/secrets
volumes:
- name: agent-secrets
emptyDir:
medium: Memory Would it be possible to make the path for the volumeMount |
Hi, @sando38, thanks for using Bank-Vaults! Please add these as separate issues to the project so we can track them independently. Meanwhile, we are taking a look at the problem! |
Thanks! Will do so. And thanks for offering bank vaults! |
#149
#231
and any other requested
The text was updated successfully, but these errors were encountered: