datadog.endpointConfigName does not respect fullnameOverride or nameOverride

[sdwa0]

Pre-submission Checklist

• I have searched existing issues and this is not a duplicate
• This is a Helm chart issue, not a Datadog product/service problem

Helm chart name

datadog

Helm chart version

3.201.7

Bug Report

What happened:

All other ConfigMap name helpers in _helpers.tpl (e.g., agents-useConfigMap-configmap-name, agents.confd-configmap-name, datadog-checksd-configmap-name, etc.) delegate to datadog.fullname, which correctly handles fullnameOverride and nameOverride values.

However, datadog.endpointConfigName constructs its name by concatenating .Release.Name (and chart alias for aliased subchart) directly, bypassing datadog.fullname entirely.

This means that if a user sets fullnameOverride or nameOverride, all other ConfigMaps will use the overridden name prefix, but the endpoint ConfigMap will still use the raw release name, causing an inconsistency.

This behavior was introduced in #2362 (tagging @fanny-jiang for visibility). A similar suggestion was previously made in #2187.

What I expected:

datadog.endpointConfigName should derive its prefix from datadog.fullname (or equivalent logic), consistent with all other ConfigMap name helpers.

Steps to Reproduce

No response

Environment

Kubernetes version:
Helm version:
Cloud provider:

Additional Context

No response

[levan-m]

@sdwa0, thanks for reporting the issue! Can you confirm if this is causing any issue during installation/upgrade or is this request to making naming consistent?

[sdwa0]

It is both. This causes issues during upgrades to newer versions for multi-alias charts where the chart aliases used contain characters not allowed in a configmap name, e.g., camel case names.

one or more objects failed to apply, reason: ConfigMap "camelCaseChartAlias-datadog-agent-endpoint-config" is invalid: metadata.name: Invalid value: "camelCaseChartAlias-datadog-agent-endpoint-config": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

There are workarounds, it would be nicer to fix this in the chart for consistency.