[ISSUE] global.labels Used in Both matchLabels and metadata.labels

[drodriguez-305]

Describe the issue:

related to: https://jira.camunda.com/browse/SUPPORT-24909

The global.labels field in the Camunda Platform Helm chart is being applied to both metadata.labels and matchLabels (selectors). This behavior is problematic because matchLabels are immutable, and dynamic or environment-specific labels cannot be safely updated in subsequent deployments.

Actual behavior:

When labels are defined in global.labels, they are applied to:

• metadata.labels (which is expected and allowed to change).
• matchLabels (used for Kubernetes selectors, which are immutable).

Expected behavior:

How to reproduce:

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

• Platform:
• Helm CLI version:
• Chart version:
• Values file:

[drodriguez-305]

@hamza-m-masood adding your comment here.
I can reproduce this.
Helm upgrading with a changed global.labels produces an error saying that matchLabels can't be changed in each component.

I'm fine with you opening a bug report on this. We could probably just take out this section in the function:
https://github.com/camunda/camunda-platform-helm/blob/36fc7f60e4aa2dc00288e91ad222[…]55b8/charts/camunda-platform-8.6/templates/camunda/_helpers.tpl

I'm fine with that part being taken out because the other labels still exist in the function.
I checked other bitnami charts hoping to see something along the lines of global.matchLabels but most charts only provide matchLabels for either ingress or networkPolicies. I did find a common function which seems useful: https://github.com/bitnami/charts/blob/b41a51d1bd04841fc108b78d3b8357a5292771c8/bitnami/common/templates/_labels.tpl#L34
This is used by the grafana chart which can be seen here:
https://github.com/bitnami/charts/blob/b41a51d1bd04841fc108b78d3b8357a5292771c8/bitnami/grafana/templates/deployment.yaml#L16C1-L21C43
it would be better to implement what the grafana chart does already. It keeps the matchLabels immutable

[larszi]

We are also facing this issue.