claude-botandClaude Opus 5
3a001c5f46
The `>=1.0.0 <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 the
cluster on a dead line while upstream had moved on to app v1.4.19.
Verified before bumping:
- The only breaking change at the 1.x->2.0.0 boundary is the relocation of
`deployment.image.*` to top-level `image.*`. This HelmRelease sets
`values: {}`, so neither key is in play and the bump is a drop-in.
- `helm template stakater/reloader --version 2.2.14` renders cleanly with
default values (rc=0, image v1.4.19).
- ClusterRole rules are byte-identical between 1.3.0 and 2.2.14 — the
cluster-wide privileges of this restart-authority controller do not change.
2.x additionally ships a namespace-scoped Role (configmaps
list/get/watch/create/update) used for leader election. Additive only.
- `kubectl kustomize kubernetes/infrastructure` renders 199 resources with the
HelmRelease resolving to the new constraint.
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 today.
Blast radius on upgrade: reloader itself rolls; the 7 annotated workloads
(apps/external-dns, apps/woodpecker-agent, apps/woodpecker-server,
home-assistant/home-assistant, home-assistant/shelly-manager,
monitoring/pve-exporter, paperless/paperless) are not restarted by a
controller upgrade alone.
Refs #426
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>