kubernetes/infrastructure/reloader/helmrelease.yaml

@@ -24,11 +24,23 @@ spec:
   chart:
     spec:
       chart: reloader
-      # Bounded to the current major: a cluster-wide restart-authority controller
-      # must not float across majors (repo pinning discipline — cf. the OpenBao
-      # chart's "chart bumps only deliberately" pin). Confirm the resolved version
-      # on first sync; bump the bound deliberately for a 2.x.
-      version: ">=1.0.0 <2.0.0"
+      # Bounded to one major: a cluster-wide restart-authority controller must not
+      # float across majors (repo pinning discipline — cf. the OpenBao chart's
+      # "chart bumps only deliberately" pin).
+      #
+      # Deliberate 1.x -> 2.x bump, 2026-07-27. The old <2.0.0 ceiling had reached
+      # its practical maximum: chart 1.3.0 (app v1.3.0) is the last 1.x ever
+      # published, so the bound was holding us on a dead line while upstream moved
+      # to app v1.4.19. The only breaking change at the 1.x->2.0.0 boundary is the
+      # relocation of `deployment.image.*` to top-level `image.*`; `values: {}`
+      # below sets neither, so nothing here is affected. Beware: Helm silently
+      # DROPS renamed/orphaned values keys instead of erroring — if image overrides
+      # are ever added here, check them against the chart schema rather than
+      # trusting a clean apply.
+      #
+      # Floored at 2.2.0 rather than 2.0.0 to skip the early 2.0/2.1 line outright;
+      # resolves to 2.2.14 (app v1.4.19) today.
+      version: ">=2.2.0 <3.0.0"
       sourceRef:
         kind: HelmRepository
         name: stakater