-
Notifications
You must be signed in to change notification settings - Fork 884
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
add support for more flexible volume mounts e.g. for use with init containers #314
add support for more flexible volume mounts e.g. for use with init containers #314
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Looks useful but this will need unit tests. You can find them in test/unit
. Let me know if you have any questions about implementing them!
Hi Jason. I'll try, I've not used these before so might have questions. I've tested the output is as expected using |
a0a10b7
to
b900fa7
Compare
…or init container add unit tests add missing braces
4675c64
to
060ea1f
Compare
@jasonodonnell Can this be merged, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like the approach for adding volumes in this PR. I agree that extraVolumes
is opinionated, so I'm going to mark that as deprecated (and begin phase out) in support of this approach.
The existing volume mounts implementation via extraVolumes is too opinionated to allow mounting volumes for custom purposes, such as installing a plugin via an init container. Personally I don't like it and would remove it completely, but for backwards compatibility I've left it and added additional server.volumes and server.volumeMounts. Examples in the values files show how this can be used.
Please consider this as it's an easy way to customise your Vault installation.