[jaeger] Add podAnnotations support to deployment

The legacy components such as query supported podAnnotations the same way
the other components still do.

This adds the podAnnotations field to the jaeger values section,
following the same pattern already used by the spark, esIndexCleaner,
esRollover, and esLookback job templates.

The previously hard-coded prometheus podAnnotations are moved to the new
values as a default setup.

Signed-off-by: Michael Jung <mike_jung@gmx.net>

Author: m-dot-jung

charts/jaeger/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: common
   repository: https://charts.bitnami.com/bitnami
-  version: 2.34.0
-digest: sha256:63de10c1f68bedef391890484e1e29f2efd54e6dc7239ca60f0a572042efd4f3
-generated: "2026-02-03T13:47:26.844621Z"
+  version: 2.36.0
+digest: sha256:a9e48d71c1ab826e89a4115379550999c1787634d834acfe22122560393685b4
+generated: "2026-02-11T16:40:36.0392565+01:00"

charts/jaeger/Chart.yaml

@@ -3,7 +3,7 @@ appVersion: 2.15.1
 description: A Jaeger Helm chart for Kubernetes
 name: jaeger
 type: application
-version: 4.5.0
+version: 4.5.1
 # Artifact Hub annotations
 # The jaeger image is whitelisted from security scanning because the reported
 # CVEs are in the upstream Alpine base image (OpenSSL libcrypto3/libssl3) and

charts/jaeger/templates/jaeger/jaeger-deploy.yaml

@@ -31,8 +31,9 @@ spec:
         {{- toYaml .Values.jaeger.podLabels | nindent 8 }}
 {{- end }}
       annotations:
-        prometheus.io/port: "8888"
-        prometheus.io/scrape: "true"
+        {{- if .Values.jaeger.podAnnotations }}
+        {{- toYaml .Values.jaeger.podAnnotations | nindent 8 }}
+        {{- end }}
     spec:
       {{- include "jaeger.imagePullSecrets" . | nindent 6 }}
       containers:

charts/jaeger/values.yaml

@@ -212,6 +212,9 @@ jaeger:
   tolerations: []
   affinity: {}
   topologySpreadContraints: []
+  podAnnotations:
+    prometheus.io/port: "8888"
+    prometheus.io/scrape: "true"
   podSecurityContext:
     runAsUser: 10001
     runAsGroup: 10001