make it possuble to just supply a full config

[trondhindenes]

I'm finding it incredibly difficult to set up a custom collector config, because I need to disable the things I don't want. I can't just supply port values if I need non-standard ones either.

Please consider making the config easier by providing an option to just supply a full config and list of ports

[JaredTan95]

have you tried --set configMap.create=false --set configMap.existingName=your-own-configmap-for-collector?

[TylerHelmuth]

You should be able to do

ports:
  custom:
    enabled: true
    containerPort: 9999
    servicePort: 9999
    hostPort: 9999
    protocol: TCP

to add custom ports to both the container and service. ports is a map so it will merge cleanly.

[TylerHelmuth]

Can you be more specific about what is difficult to configure? You can remove default components using helm's null feature such as

config:
  receivers:
    jaeger: null
    prometheus: null
    zipkin: null
  service:
    pipelines:
      traces:
        receivers:
          - otlp
      metrics: null
      logs: null

Full example: https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/examples/deployment-otlp-traces/values.yaml

[boxidau]

+1 on this issue. Having to null out the default config requires merging the nulled structure into our config which seems a little messy. Changes to the default config would then be breaking changes on chart updates.

Having a second alternative key customConfig (or similar) in values where a user can define their entire config would be much easier to deal with in cases where a user has an already well formed config they'd like to use.

The other option of an externally managed ConfigMap is okay and gives the flexibility but loses the auto-reload functionality on config updates