[Feature]: Support different configmap for the different components of Jaeger in helm chart Jaeger v2

[LittleGoWitch]

Requirement

In the Branch v2 of this repo, it only supports one user-config for all-in-one architecture, I want to support scalable components of Jaeger version 2 in the helm chart.

Problem

In the Branch v2 of this repo, it only supports one user-config for all-in-one architecture, I want to have different configmap for different components of Jaeger: jaeger-agent, jaeger-collector, jaeger-ingester, jaeger-query all of them has a mapping configmap of user-config so you can not use different config for each one of them as mentioned in here
Also these images(jaeger-agent, jaeger-collector, jaeger-ingester, jaeger-query) doesn't support version 2 image and it has a lot of unnecessary ENV variables if it's migrated to version 2

Proposal

Upgrade jaeger-agent, jaeger-collector, jaeger-ingester, jaeger-query to the jaegertracing/jaeger image and support different configmap for each one of them separately

Open questions

No response

[yurishkuro]

Upgrade jaeger-agent, jaeger-collector, jaeger-ingester, jaeger-query to the jaegertracing/jaeger

it sounds like you're suggesting migrating v1 component charts into v2 Jaeger. This was not the plan. v2 chart is independent of v1 chart. With v2 chart you can run Jaeger in any role by giving it the desired config. I am not sure if it's necessary to have the v2 chart itself understand the different roles - the deployment strategies would be different, so can't it be the responsibility of the user? It does need documentation.

[amashaye]

Yeah it definitely needs better documentation.
But if I understood from the documentation of Architecture in v2 if we want to have the production strategy jaeger will take different roles. and in the helm chart v2 we only have one role which will deploy all-in-one strategy and the configmap user-config has the potential to be used only for one role so the role configmap is managed by the .Values.collector.extraConfigmapMounts and .Values.collector.cmdlineParams and user-config configmap should be only with the common config. So I think if the helm chart supports different configmap user-config for different role it will make the production strategy deployment much easier.

[yurishkuro]

You can run helm multiple times, each with different configuration for a given role.