Post

DBeaver

DBeaver

DBeaver (CloudBeaver)

Purpose

CloudBeaver — the web edition of DBeaver — provides a browser-based SQL client for the databases running in the homelab (Postgres, etc).

Deployment

ItemValue
Imagedbeaver/cloudbeaver:26.2.3
Namespacedefault
Replicas1 (strategy: Recreate)
Node placementx86 k3s LXC nodes (nodeSelector kubernetes.io/arch: amd64 + picluster/lxc: "true"); follows its local-zfs volume
Service typeClusterIP, port 8978
Storagedbeaver-data-zfs PVC, 5Gi, local-zfs storage class
IngressTraefik IngressRoute, TLS via shared local-example-com-tls cert

reloader.stakater.com/auto: "true" is set on the Deployment.

Storage

The dbeaver-data-zfs PVC is mounted at /opt/cloudbeaver/workspace, persisting connection configs, credentials, and workspace settings across restarts. Like every app volume in the cluster since the October 2026 move to x86 LXC nodes, it is a node-local local-zfs volume: a directory on that node’s ZFS-backed volume (a zvol on the TrueNAS NVMe pool, attached to the k3s LXC node), so the pod is scheduled where its volume is.

Ingress

Routed via Traefik IngressRoute at:

  • dbeaver.prod-k3s.homelab.example (with default-headers middleware)

Resources

 RequestsLimits
CPU50m500m
Memory256Mi512Mi
This post is licensed under CC BY 4.0 by the author.