You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I want to define a basic set of configuration in the config block, but also allow for arbitrary configurations to be added via an additional configmap. In my case I'm deploying the operator as a Helm subchart and want users of my chart to be able to pass arbitrary blocks of configurations that I can't know ahead of time.
Describe the solution you'd like
I want to mount a configmap which contains additional configuration to be passed to controller, and then add a config: /path/to/additional-config.yaml arg that would be added to the container's args.
Currently this doesn't work because the operator ignores the config key from the args part of the spec.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
@wperron we have a long standing open issue here #1906, for now, i would recommend checking out the opentelemetry-kube-stack chart which already does the merging via helm.
Component(s)
collector
Is your feature request related to a problem? Please describe.
I want to define a basic set of configuration in the
config
block, but also allow for arbitrary configurations to be added via an additional configmap. In my case I'm deploying the operator as a Helm subchart and want users of my chart to be able to pass arbitrary blocks of configurations that I can't know ahead of time.Describe the solution you'd like
I want to mount a configmap which contains additional configuration to be passed to controller, and then add a
config: /path/to/additional-config.yaml
arg that would be added to the container's args.Currently this doesn't work because the operator ignores the
config
key from theargs
part of the spec.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: