fix(gotify): run gotify-db with 2 instances, not 3 #99

Merged
rock merged 2 commits from fix/gotify-db-two-instances into main 2026-11-03 21:24:19 +00:00
Owner

The file header always said 2 instances while the spec said 3. The third never ran: gotify-db-3's volume held one replica that could not start because talos-cp-2 disk2 is at 2.9% free, which left the cluster permanently in 'Creating a new replica' with a degraded Longhorn volume.

Two replicas on two nodes is the redundancy that actually exists. Found while replacing a corrupt replica whose filesystem had been remounted read-only.

The file header always said 2 instances while the spec said 3. The third never ran: gotify-db-3's volume held one replica that could not start because talos-cp-2 disk2 is at 2.9% free, which left the cluster permanently in 'Creating a new replica' with a degraded Longhorn volume. Two replicas on two nodes is the redundancy that actually exists. Found while replacing a corrupt replica whose filesystem had been remounted read-only.
rock added 2 commits 2026-11-03 21:24:15 +00:00
poimen-memory is a ClusterIP service on :8080, so a local pi session had no
route to the API. This adds an edge Ingress on the same nginx class and the
same Cloudflare-terminated shape as the frontend ingress.

Auth stays ZITADEL JWT (MEM_AUTH_MODE=jwt): a request without a valid bearer
token gets 401, so exposing the route does not expose the data.

Requires one Cloudflare proxied A record: api-poimen.riotpiao.com -> 192.168.1.160
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.
rock merged commit c8e8b9532d into main 2026-11-03 21:24:19 +00:00
Sign in to join this conversation.