[flux2] support containerName for deployments can be customised

[lkaluza-fadi]

Is your feature request related to a problem ?

Currently all containerNames in a flux deployment/pods are called manager. As we are using datadog as a monitoring tool its hard to figure out which container has maybe some resource issues because they are all named the same.

Describe the solution you'd like.

We would like to have the option to configure the name of the container in the helm_release like:

helmController:
  container:
    name: <some-container-name>
sourceController:
  container:
    name: <some-container-name>
etc...

Describe alternatives you've considered.

None

Additional context.

No response

[stefanprodan]

Datadog should add the deployment name to its report, the manager naming is a convention we have in Flux upstream and this chart should be as close as possible to it.

[lkaluza-fadi]

@stefanprodan I don't understand the connection between the flux upstream and the name of the Kubernetes resources like container name. Could you elaborate this a bit more? Is it realy not possible to have an option of configuring different names and having the default as manager?

[onedr0p]

The container name manager for all the controllers is standard across all methods of installing Flux.

I'm with Stefan on this one, your monitoring tool (datadog) should already have the metric data enriched with deployment name. It sounds like your processes could be improved upon here.