-
Notifications
You must be signed in to change notification settings - Fork 506
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
Added more flexible volume variables #151
Conversation
I've realized that we have no automated test that check that changes to the values.yaml like these are actually valid when they are used instead of their defaults of empty. I tested locally but would be good to run it through the workflow with real values. Should one of our CI scenarios actually fill out every possible values.yaml setting? |
That would be useful. But they have be different from the default values. Not sure it's possible to cover all options within one scenario |
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.
LGTM. Please update the version. The previous PR got merged sooner
Done |
This PR adds new
extraVolumes
andextraVolumeMounts
variable and deprecatesextraConfigMapMounts
,extraHostPathMounts
, andsecretMounts
.Going forward,
extraVolumes
andextraVolumeMounts
will allow more flexiblevolumes
andvolumeMounts
by putting the configuration in the hands of the user.Fixes #133