chore(deps): otel-collector 0.169.0, with the image following the chart

addons/observability/otel-agent/values.yaml

@@ -18,7 +18,14 @@ mode: daemonset
 # artifact. image.repository is mandatory — chart >=0.110 ships no default.
 image:
   repository: otel/opentelemetry-collector-contrib
-  tag: "0.157.0"
+  # No `tag:` deliberately. The chart renders
+  # `.Values.image.tag | default .Chart.AppVersion`, so leaving it unset makes the
+  # image follow the chart pin instead of being maintained beside it. A hand-set
+  # tag here has to be moved by a second act nothing performs or checks — Renovate
+  # sees the chart (argocd manager) and not this file — which is how the two spent
+  # a stretch a release apart. The contrib distro publishes the same version
+  # numbers as the core collector the appVersion tracks, verified against the
+  # registry for the version this pin resolves to.
 
 # Stable object names (DaemonSet/ConfigMap/ClusterRole) independent of the ArgoCD
 # release name, so the gateway address and RBAC bindings don't shift on a rename.

addons/observability/otel-gateway-floor/values.yaml

@@ -17,7 +17,14 @@ mode: deployment
 
 image:
   repository: otel/opentelemetry-collector-contrib
-  tag: '0.157.0'
+  # No `tag:` deliberately. The chart renders
+  # `.Values.image.tag | default .Chart.AppVersion`, so leaving it unset makes the
+  # image follow the chart pin instead of being maintained beside it. A hand-set
+  # tag here has to be moved by a second act nothing performs or checks — Renovate
+  # sees the chart (argocd manager) and not this file — which is how the two spent
+  # a stretch a release apart. The contrib distro publishes the same version
+  # numbers as the core collector the appVersion tracks, verified against the
+  # registry for the version this pin resolves to.
 
 # Identical object names to the full tier, deliberately: the node agent forwards
 # to otel-gateway.monitoring.svc.cluster.local:4317 and the telemetry alias

addons/observability/otel-gateway/values.yaml

@@ -15,7 +15,14 @@ mode: deployment
 
 image:
   repository: otel/opentelemetry-collector-contrib
-  tag: "0.157.0"
+  # No `tag:` deliberately. The chart renders
+  # `.Values.image.tag | default .Chart.AppVersion`, so leaving it unset makes the
+  # image follow the chart pin instead of being maintained beside it. A hand-set
+  # tag here has to be moved by a second act nothing performs or checks — Renovate
+  # sees the chart (argocd manager) and not this file — which is how the two spent
+  # a stretch a release apart. The contrib distro publishes the same version
+  # numbers as the core collector the appVersion tracks, verified against the
+  # registry for the version this pin resolves to.
 
 # Stable object names — the Service the agents forward to (otel-gateway) and the
 # SA the AMP Pod Identity association binds must not shift on an ArgoCD rename.

applicationsets/addons-otel-agent.yaml

@@ -40,7 +40,7 @@ spec:
       sources:
         - repoURL: https://open-telemetry.github.io/opentelemetry-helm-charts
           chart: opentelemetry-collector
-          targetRevision: 0.166.0
+          targetRevision: 0.169.0
           helm:
             releaseName: otel-agent
             valueFiles:

applicationsets/addons-otel-gateway-floor.yaml

@@ -41,7 +41,7 @@ spec:
       sources:
         - repoURL: https://open-telemetry.github.io/opentelemetry-helm-charts
           chart: opentelemetry-collector
-          targetRevision: 0.166.0
+          targetRevision: 0.169.0
           helm:
             releaseName: otel-gateway
             # extraEnvs is a list, so Helm replaces it wholesale — valuesObject

applicationsets/addons-otel-gateway.yaml

@@ -38,7 +38,7 @@ spec:
       sources:
         - repoURL: https://open-telemetry.github.io/opentelemetry-helm-charts
           chart: opentelemetry-collector
-          targetRevision: 0.166.0
+          targetRevision: 0.169.0
           helm:
             releaseName: otel-gateway
             # extraEnvs is a list, so Helm replaces it wholesale — valuesObject