fix(ical-proxy): pin the image so a new build actually rolls

:latest never rolls. The tag moves when a build publishes, but nothing tells the Deployment: the pod template is unchanged, so Kubernetes has no reason to replace anything. Nothing else covers it either. This image is deliberately not enrolled in Flux image automation — kubernetes/infrastructure/image-automation/README.md lists ghcr.io/konairius/ical-proxy as having "only main, latest, and main-<sha> commit builds; no release tags", so no ImagePolicy watches it. The two pods have been running a 21-day-old image while :latest moved underneath them, and the only way to pick up a new build was a manual restart, which leaves no record anywhere. Pinning makes the rollout a git change. Flux applies the new pod template, Kubernetes rolls it, and what is RUNNING becomes recoverable from this repo instead of "whatever :latest meant the last time a pod happened to restart". main-99a912b is the merge of konairius/ical-proxy#12, which adds the summary_match and summary_replace parameters. The waste calendar needs them to strip "| Abfuhrkalender - Landkreis Amberg-Sulzbach" from every collection — the feed repeats the whole calendar's name on each event, and no consumer can shorten it after the fact. Bumping this tag is now a manual, reviewed edit. Format is main-<short-sha>, from docker/metadata-action type=sha with the branch as prefix.
Merge pull request 'fix(trmnl): let Reloader restart the renderer on config and secret changes' (#489 ) from fix-trmnl-renderer-reloader into master
2026-08-13 21:38:29 +02:00 · 2026-08-12 20:23:03 +00:00
1 changed files with 27 additions and 1 deletions
@@ -17,7 +17,33 @@ spec:
    spec:
      containers:
        - name: ical-proxy
-          image: ghcr.io/konairius/ical-proxy:latest
+          # Pinned to a commit build rather than :latest.
+          #
+          # :latest never rolls. The tag moves when a build publishes, but
+          # nothing tells the Deployment about it: the pod template is
+          # unchanged, so Kubernetes has no reason to replace anything, and
+          # this image is deliberately NOT enrolled in Flux image automation
+          # — see kubernetes/infrastructure/image-automation/README.md, which
+          # lists ghcr.io/konairius/ical-proxy as having "only main, latest,
+          # and main-<sha> commit builds; no release tags", so there is no
+          # ImagePolicy watching it. The pods therefore sat on a 21-day-old
+          # image while :latest moved underneath them, and the only way to
+          # pick up a new build was a manual restart.
+          #
+          # A pinned tag makes the rollout a git change: Flux applies the new
+          # pod template and Kubernetes rolls it, which is also what makes
+          # what is RUNNING recoverable from this repo rather than "whatever
+          # :latest meant the last time a pod happened to restart".
+          #
+          # main-99a912b is the merge of konairius/ical-proxy#12, which adds
+          # the summary_match/summary_replace parameters this deployment
+          # needs to strip "| Abfuhrkalender - Landkreis Amberg-Sulzbach"
+          # from every waste collection.
+          #
+          # Bumping this is a manual, reviewed edit. The tag format is
+          # main-<short-sha> (docker/metadata-action type=sha with the branch
+          # as prefix).
+          image: ghcr.io/konairius/ical-proxy:main-99a912b
          ports:
            - containerPort: 8080
              name: http