Allow extraLabels to be set

[mclueppers]

Hi,

I'm looking forward to using the Helm charts to deploy DT on my K8s cluster. But my company is usings admission controllers that will verify the existence of particular labels. Since they're not part of the produced templates, I cannot test any deployments. For this reason I'd like to ask for the introduction of extraLabels values key that can accept multiple K/V entries.

[dhalperovich]

Good day. I would appreciate those extraLabels or podLables as well.

[nscuro]

Can we get some clarification as to what the extraLabels need to be applied to? Should there be a global extraLabels variable, or would every resource need separate extraLabels? And for Deployments , Jobs, and StatefulSets, do we need a separate labels value for the Pods they are creating?

[mclueppers]

IMO we need a global extraLabels that will be set for all resources, and individual extraLabels that can be added on top of the global ones. I personally sometimes use Blue/Green deployments and I toggle active slice at Service level, hence the need for an extra granularity.

[enys]

Extrapolating on this, a common scenario is to add extra labels on the service monitor such as: release: kube-prometheus-stack allowing Prometheus operator to pickup the service monitor