From e733bd6f7b0439f2b19b8099fbb183dd3ec7c493 Mon Sep 17 00:00:00 2001 From: Flux Image Automation Date: Fri, 16 Oct 2026 09:33:08 +0000 Subject: [PATCH 1/3] chore(image-automation): bump docker.gitea.com/gitea-mcp-server:1.9.0 Updates managed by image-automation-controller. --- kubernetes/apps/gitea-mcp/deployment.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kubernetes/apps/gitea-mcp/deployment.yaml b/kubernetes/apps/gitea-mcp/deployment.yaml index 0794324b..adfcf5ae 100644 --- a/kubernetes/apps/gitea-mcp/deployment.yaml +++ b/kubernetes/apps/gitea-mcp/deployment.yaml @@ -23,7 +23,7 @@ spec: type: RuntimeDefault containers: - name: gitea-mcp - image: docker.gitea.com/gitea-mcp-server:1.8.1 # {"$imagepolicy": "flux-system:gitea-mcp"} + image: docker.gitea.com/gitea-mcp-server:1.9.0 # {"$imagepolicy": "flux-system:gitea-mcp"} # Image has no ENTRYPOINT (binary is in CMD), so args alone would replace it. command: - /app/gitea-mcp From b989f3eea7769b0e38e5fc28dd4207472aff43c1 Mon Sep 17 00:00:00 2001 From: Claude Bot Date: Fri, 16 Oct 2026 21:13:36 +0200 Subject: [PATCH 2/3] fix(woodpecker): recover wp-pg from the prefix it archives to wp-pg-store-source, the recovery source of wp-pg's bootstrap.recovery, pointed at s3://renner-uno-k8s-cnpg/wp-pg: the prefix of the retired apps/wp-pg. Since the namespace move wp-pg archives to wp-pg-woodpecker (wp-pg-store). A cold rebuild would therefore have restored woodpecker as of 2026-08-18 and reported success. Bucket, listed read-only 2026-10-16: - wp-pg/wp-pg/base: newest 20260818T023502 - wp-pg-woodpecker/wp-pg/base: 20260916T024000 .. 20261016T024000 (daily), wals/ through timeline 6 (00000006.history from 2026-09-23) The source now reads wp-pg-woodpecker; serverName stays wp-pg, the name the live cluster archives under. bootstrap.recovery is honoured only when PGDATA is absent, so the running cluster is unaffected. The old prefix wp-pg is no longer referenced and keeps its objects; nothing applies retention to it. Co-Authored-By: Claude Opus 5.5 --- kubernetes/apps/woodpecker/objectstore.yaml | 21 +++++++-------------- 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/kubernetes/apps/woodpecker/objectstore.yaml b/kubernetes/apps/woodpecker/objectstore.yaml index e00eb14a..ef132eb7 100644 --- a/kubernetes/apps/woodpecker/objectstore.yaml +++ b/kubernetes/apps/woodpecker/objectstore.yaml @@ -1,10 +1,5 @@ --- -# RECOVERY SOURCE — read-only. The prefix the retired `apps/wp-pg` archived to. -# -# Kept after the migration on purpose. Nothing writes to it, and the backups -# under it age out on their own retention, but while they last this is a second, -# independent restore point that predates the move — worth having until the new -# prefix has a meaningful backup history of its own. +# RECOVERY SOURCE — read-only. The prefix wp-pg archives to (wp-pg-store below). # # serverName on the consuming externalCluster must be `wp-pg`, the name of the # cluster that produced these backups. @@ -15,7 +10,7 @@ metadata: namespace: woodpecker spec: configuration: - destinationPath: s3://renner-uno-k8s-cnpg/wp-pg + destinationPath: s3://renner-uno-k8s-cnpg/wp-pg-woodpecker endpointURL: https://fsn1.your-objectstorage.com s3Credentials: accessKeyId: @@ -31,15 +26,13 @@ spec: compression: gzip data: compression: gzip - # No retentionPolicy: this store is a read source during the migration, and - # the old cluster in `apps` owns the lifecycle of the data underneath it. + # No retentionPolicy: wp-pg-store owns the lifecycle of this prefix. --- -# ARCHIVING TARGET — a DIFFERENT prefix from the source, deliberately. +# ARCHIVING TARGET. # -# Two clusters archiving WAL to one destinationPath interleave their streams and -# corrupt both. That mattered during the parallel-run window; it still matters -# now, because the source prefix above is retained and must stay frozen for the -# independent restore point it provides. +# Not s3://renner-uno-k8s-cnpg/wp-pg: the retired `apps/wp-pg` archived there, +# and two clusters archiving WAL to one destinationPath interleave their streams +# and corrupt both. apiVersion: barmancloud.cnpg.io/v1 kind: ObjectStore metadata: From 0111139a33ab251c078e9eb097d6ea878944f383 Mon Sep 17 00:00:00 2001 From: Flux Image Automation Date: Fri, 16 Oct 2026 20:49:13 +0000 Subject: [PATCH 3/3] chore(image-automation): bump ghcr.io/home-assistant/home-assistant:2026.10.2 Updates managed by image-automation-controller. --- kubernetes/apps/home-assistant/deployment.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kubernetes/apps/home-assistant/deployment.yaml b/kubernetes/apps/home-assistant/deployment.yaml index dbaf7cf2..5377b5b9 100644 --- a/kubernetes/apps/home-assistant/deployment.yaml +++ b/kubernetes/apps/home-assistant/deployment.yaml @@ -95,7 +95,7 @@ spec: memory: 32Mi containers: - name: home-assistant - image: ghcr.io/home-assistant/home-assistant:2026.10.1 # {"$imagepolicy": "flux-system:home-assistant"} + image: ghcr.io/home-assistant/home-assistant:2026.10.2 # {"$imagepolicy": "flux-system:home-assistant"} env: - name: TZ value: Europe/Berlin