From c404791ca2e880116fb839d6e03a19650373e6fd Mon Sep 17 00:00:00 2001
From: stxkxs <139715017+stxkxs@users.noreply.github.com>
Date: Sat, 8 Aug 2026 13:52:29 -0700
Subject: [PATCH] chore(deps): otel-collector 0.169.0, with the image following
 the chart
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Mirrors eks-gitops 9c7ce04.

The chart moves 0.166.0 -> 0.169.0 and the hand-set image tag comes out. Chart
0.166.0 declares appVersion 0.157.0 and this file pinned the image at 0.157.0,
so the two agreed by hand; 0.169.0 declares 0.158.0, so bumping the chart alone
would have opened a divergence with the chart ahead of the binary it names.

mirror-check compares chart versions and nothing else, so it would never have
reported that drift — the same blind spot that lets a velero plugin image sit
three minors from its counterpart across the two repositories. Deleting the tag
removes the second fact rather than adding a check for it: the chart renders
`.Values.image.tag | default .Chart.AppVersion`, so the image is now a function
of the pin.

Rendered output resolves to otel/opentelemetry-collector-contrib:0.158.0, which
confirms the default is reached rather than assumed. upstream.ref moves to
9c7ce04, and `mirror-check sync` re-pinned zero slices — the hand-written
version already matched what eks-gitops pins. Full check: 32 charts match, 12
declared divergences, 2 CRD installers answered.
---
 stack/observability/otel-collector/install.sh  | 2 +-
 stack/observability/otel-collector/values.yaml | 7 ++++++-
 stack/upstream.json                            | 2 +-
 3 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/stack/observability/otel-collector/install.sh b/stack/observability/otel-collector/install.sh
index 3e59110..d76d2a5 100755
--- a/stack/observability/otel-collector/install.sh
+++ b/stack/observability/otel-collector/install.sh
@@ -14,6 +14,6 @@ kubectl create namespace monitoring --dry-run=client -o yaml | kubectl apply -f
 
 helm upgrade --install otel-collector open-telemetry/opentelemetry-collector \
   --namespace monitoring \
-  --version 0.166.0 \
+  --version 0.169.0 \
   --values "${SCRIPT_DIR}/values.yaml" \
   --wait
diff --git a/stack/observability/otel-collector/values.yaml b/stack/observability/otel-collector/values.yaml
index 4ddcd2a..d049628 100644
--- a/stack/observability/otel-collector/values.yaml
+++ b/stack/observability/otel-collector/values.yaml
@@ -28,7 +28,12 @@ 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 a second fact maintained beside
+  # it — mirror-check compares chart versions and would never see the two drift.
+  # The contrib distro publishes the same version numbers as the core collector
+  # the appVersion tracks.
 
 # Stable object name, matching upstream — the `telemetry` Service alias below
 # selects on it, and a rename would break the tenant contract silently.
diff --git a/stack/upstream.json b/stack/upstream.json
index e915465..52dd023 100644
--- a/stack/upstream.json
+++ b/stack/upstream.json
@@ -3,7 +3,7 @@
   "upstream": {
     "repository": "nanohype/eks-gitops",
     "path": "applicationsets",
-    "ref": "46f9f8e94d7d63a7092007f22dcf77a7de6fd9e5"
+    "ref": "9c7ce0476cd44aa2637b893f592a1f40fda99f81"
   },
   "divergences": [
     {