-
Notifications
You must be signed in to change notification settings - Fork 469
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
[opentelemetry-collector] Allow more flexibility around volumes/envs #1168
Comments
Any thoughts on this? @povilasv @JaredTan95 @TylerHelmuth |
This feels like a consequence of helm and lists. The collector chart doesn't provide any default values for I don't like the idea of adding multiple fields to do the same thing. In some of our other charts we have a concept of |
Sorry just now getting back to this. Are you saying the parent chart should add |
Would it be possible to pick this convo back up? @povilasv @TylerHelmuth |
Hi all,
When using opentelemetry-collector chart as a subchart, the only options the parent chart has to configure volumes is through
extraVolumes/extraVolumeMounts
fields. Which makes it hard for the parent chart to expose those fields as configurable to its users.For example given the following scenario
For users of the parent chart to add more volumes to telemetryCollector subchart they would need to redefine the entire block of extraVolumes since its an array type. This UX isn't very friendly to changes
The scenario above also applies to configuring environment variables.
Solution Options:
The text was updated successfully, but these errors were encountered: