Files
homelab-k3s/apps/dashwise/service.yaml
T
jasonwitty 7b084dbddd
Validate and Deploy to K3s / validate (push) Successful in 19s
Validate and Deploy to K3s / deploy (push) Successful in 23s
Add dashwise and tududi
Two self-hosted apps behind traefik, both keeping their state on the
GlusterFS volume that is mounted on every node:

- dashwise (home.wittyoneoff.com) is an all-in-one image running its web
  server, a bundled PocketBase and valkey side by side. Only port 3000 is
  published: the frontend resolves its backend as window.location.origin
  and every PocketBase call is made server-side, so 8090 stays inside the
  pod. It is on the service so the PocketBase admin UI can be reached with
  kubectl port-forward.

- tududi (tududi.wittyoneoff.com) stores a SQLite database and user
  uploads. Both are VOLUMEs in the image, so both are backed by the claim
  -- as one volume mounted twice with subPath, because naming the same
  claim as two volume entries wedges kubelet, which is what happened with
  limesurvey.

Both images are pinned to tags that publish an arm64 manifest. dashwise
:latest and :stable are amd64 only and would not start on these nodes.

Namespaces and secrets are applied out of band, as with the other apps.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-12 12:46:58 -07:00

19 lines
437 B
YAML

apiVersion: v1
kind: Service
metadata:
name: dashwise
namespace: dashwise
spec:
type: ClusterIP
selector:
app.kubernetes.io/name: dashwise
ports:
- name: http
port: 3000
targetPort: http
# PocketBase is deliberately NOT published through the ingress; this port
# exists so its admin UI can be reached with `kubectl port-forward`.
- name: pocketbase
port: 8090
targetPort: pocketbase