From 1bfe08eeb80c308b8960e76e880ba57ff8e86fe6 Mon Sep 17 00:00:00 2001 From: rock Date: Wed, 4 Nov 2026 05:24:09 +0800 Subject: [PATCH] fix(gotify): run gotify-db with 2 instances, not 3 The header of this file always said 2 instances while the spec said 3. The third never ran: gotify-db-3's volume held a single replica that could not start, because talos-cp-2 disk2 is at 2.9% free. That left the cluster permanently in 'Creating a new replica' with one degraded Longhorn volume. Two replicas on two different nodes is the redundancy that actually exists. --- k8s/apps/gotify/db.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/k8s/apps/gotify/db.yaml b/k8s/apps/gotify/db.yaml index c581253..b3792e3 100644 --- a/k8s/apps/gotify/db.yaml +++ b/k8s/apps/gotify/db.yaml @@ -8,7 +8,11 @@ metadata: annotations: argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true spec: - instances: 3 + # 2, not 3. The file's own header always said 2, and the third instance never + # existed as a running pod: its volume only ever held a replica that could not + # start, because talos-cp-2 disk2 has no free space. A third replica on a disk + # that cannot host it is not redundancy, it is a permanent degraded volume. + instances: 2 imageName: ghcr.io/cloudnative-pg/postgresql:16.2 bootstrap: initdb: