Paul Payne
4d983819c9
feat(synapse): update ingress to use traefik ingress class and bump version feat(syncthing-discovery): introduce syncthing discovery service with deployment and ingress feat(syncthing-relay): add syncthing relay server with deployment and ingress configuration fix(taiga): update liveness and readiness probes to use tcpSocket for health checks fix(taiga): change PVC access mode to ReadWriteMany for media and static storage feat(traefik): add icon and ignore rules for traefik service docs(ushahidi): add notes for Redis configuration and Laravel startup probe adjustments feat(ushahidi): implement dedicated Redis deployment for Ushahidi fix(vllm): update deployment strategy and readiness/liveness probes for improved stability fix(writefreely): pin writefreely image version to v0.15.1 for consistency docs(zulip): add notes for TLS-terminating reverse proxy configuration and expected behavior
918 B
918 B
Gancio — Notes
"Non empty db" crash on re-deploy
Gancio stores its setup state in config.json on the data PVC. If the PVC is lost or the app is
deleted and redeployed against an existing database, Gancio finds a non-empty DB but no
config.json and refuses to start: "Non empty db! Please move your current db elsewhere than retry."
Fix: drop and recreate the public schema, then restart the deployment:
kubectl exec -n postgres <postgres-pod> -- psql -U postgres gancio \
-c "DROP SCHEMA public CASCADE; CREATE SCHEMA public; GRANT ALL ON SCHEMA public TO gancio; GRANT ALL ON SCHEMA public TO public;"
kubectl scale deployment -n gancio gancio --replicas=0
# wait for pod to terminate
kubectl scale deployment -n gancio gancio --replicas=1
Scale down before dropping the schema to release the database connection first. This only affects re-deployments; fresh installs work fine.