-
Notifications
You must be signed in to change notification settings - Fork 168
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
Support for Vault Namespace #20
Comments
We can add an annotation to do this. |
@jasonodonnell @darren-welab can you please provide an example on how to specify the vault namespace? The current vault stanza doesn't have an option for namespace (https://www.vaultproject.io/docs/agent/index.html#vault-stanza). I am not looking at the right place? Or, this doesn't work with vault namespaces currently? Thanks! |
There's no annotations for namespaces at this time, however you can mount a custom configuration file to do it https://www.vaultproject.io/docs/platform/k8s/injector/examples.html#configmap-example |
I am using that example (just config-init.hcl), but how I specify the vault namespace? I thought it would be under "vault" and that's why I checked the Vault stanza. |
@ecejas My apologies, I was mistaken, there's not a Vault namespace setting in the configuration file (there's one under the method stanza, but it's not the Vault namespace). It looks like only an environment variable will do, which is currently not possible with this version of Vault K8s. We expect to have namespace support in 0.2.0, so look for that once it releases. |
Implementation outlined in #55 |
The enterprise vault supports vault namespaces, but it seems that none of the annotations support it.
Something like
It seems that the only way to do so is by mounting my own configuration files using configmap.
Perhaps I missed something, please advise. Thanks!
The text was updated successfully, but these errors were encountered: