Kubernetes

Savvy runs on Kubernetes as a single-replica Deployment backed by a PersistentVolumeClaim mounted at /data.

Key requirements

• Storage: one PersistentVolumeClaim mounted at /data (the SQLite database and uploads). Use a real block/file volume, not a shared network mount.
• Update strategy: strategy: { type: Recreate } — never RollingUpdate.
• Security context: the container runs as non-root (www-data, uid 82). Grant the NET_BIND_SERVICE capability so it can bind port 80.

Probes

Wire the Kubernetes probes to the health endpoints. The startup probe gives the app time to run migrations before liveness kicks in:

        startupProbe:
          httpGet: { path: /livez, port: 80 }
          periodSeconds: 3
          failureThreshold: 30
        livenessProbe:
          httpGet: { path: /livez, port: 80 }
          periodSeconds: 10
        readinessProbe:
          httpGet: { path: /readyz, port: 80 }
          periodSeconds: 10

Remember to set APP_URL (and TZ) in the pod's env, matching the public URL your Ingress/Gateway serves Savvy on — see Installation.