Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Is your feature request related to a problem? Please describe.

I am deploying the Consul Helm chart via Flux and I need to update the Datadog tags that are specified in the StatefulSet pod spec.

While I can provide my own tags through .Values.global.extraLabels or .Values.server.extraLabels, Flux does not handle this and fails to update the resources due to duplicate keys being found in the resulting YAML. This describes the issue.

This is the error I see when I try to upgrade the chart.

Helm upgrade failed for release consul/consul with chart [email protected]: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors:
        line 41: mapping key "tags.datadoghq.com/env" already defined at line 39
        line 42: mapping key "tags.datadoghq.com/service" already defined at line 40

Feature Description

It would be great if the the Datadog tags could be modified through additional values in .Values.global.metrics.datadog so that I could continue to manage the deployment with Flux.

Use Case(s)

1. Running Consul server with Datadog enabled
2. Needing to override the Helm chart supplied Datadog tags
3. Deploying with Flux

I am using version 1.7.1 of the Helm chart.

Contributions