Problem
hyperdx.deployment.annotations currently renders on spec.template.metadata.annotations, so it configures HyperDX pod annotations. The name does not make that scope clear, and the chart does not expose a value for annotations on the HyperDX Deployment object itself (metadata.annotations).
Proposed change
Expose two explicit, backward-compatible values:
hyperdx.deployment.deploymentAnnotations for Deployment metadata.annotations
hyperdx.deployment.podAnnotations for spec.template.metadata.annotations
Keep hyperdx.deployment.annotations as a deprecated pod annotation alias so existing values continue to work. When both pod annotation maps contain the same key, podAnnotations should take precedence.
For example:
hyperdx:
deployment:
deploymentAnnotations:
example.com/controller: "enabled"
podAnnotations:
example.com/pod: "enabled"
All three values default to empty maps.
Problem
hyperdx.deployment.annotationscurrently renders onspec.template.metadata.annotations, so it configures HyperDX pod annotations. The name does not make that scope clear, and the chart does not expose a value for annotations on the HyperDX Deployment object itself (metadata.annotations).Proposed change
Expose two explicit, backward-compatible values:
hyperdx.deployment.deploymentAnnotationsfor Deploymentmetadata.annotationshyperdx.deployment.podAnnotationsforspec.template.metadata.annotationsKeep
hyperdx.deployment.annotationsas a deprecated pod annotation alias so existing values continue to work. When both pod annotation maps contain the same key,podAnnotationsshould take precedence.For example:
All three values default to empty maps.