Import manifests reverse-engineered from live cluster

Captured 2026-07-26 from rpi-master (k3s v1.30.3) and cleaned of runtime
fields. Six apps as per-app kustomizations: vaultwarden, searxng,
home-assistant, nginx, pihole(+unbound), unified-streaming.

Intentional divergences from live state:
- pihole WEBPASSWORD and USP_LICENSE_KEY moved from inline plaintext env
  to secretKeyRef (secrets gitignored; templates in secret.example.yaml)
- HA ingress defaultBackend fixed (pointed at nonexistent service)
- unifiedstreaming-svc kept as ClusterIP (LoadBalancer could never bind
  port 80 behind svclb-traefik)

Validated against the live cluster with kubectl apply --dry-run=server:
no immutable-field conflicts; one-time kubectl replace procedure for the
two env->secretKeyRef migrations documented in README.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
jasonwitty
2026-07-26 02:13:56 -07:00
parent ec9b422f87
commit 8afac39d03
40 changed files with 1179 additions and 1 deletions
+75
View File
@@ -0,0 +1,75 @@
# Originally installed via helm chart vaultwarden-5.1.0 (release record no longer
# in cluster); managed as a raw manifest since. Selector labels are immutable —
# do not change them.
apiVersion: apps/v1
kind: Deployment
metadata:
name: bitwarden-vaultwarden
namespace: bitwarden
labels:
app.kubernetes.io/instance: bitwarden
app.kubernetes.io/name: vaultwarden
spec:
replicas: 1
revisionHistoryLimit: 3
selector:
matchLabels:
app.kubernetes.io/instance: bitwarden
app.kubernetes.io/name: vaultwarden
strategy:
type: Recreate
template:
metadata:
labels:
app.kubernetes.io/instance: bitwarden
app.kubernetes.io/name: vaultwarden
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: cpu
operator: In
values:
- arm
- key: controller
operator: NotIn
values:
- "true"
containers:
- name: bitwarden-vaultwarden
image: vaultwarden/server:1.35.4
imagePullPolicy: IfNotPresent
env:
- name: DATA_FOLDER
value: config
ports:
- name: http
containerPort: 80
protocol: TCP
- name: websocket
containerPort: 3012
protocol: TCP
startupProbe:
tcpSocket:
port: 80
failureThreshold: 30
periodSeconds: 5
livenessProbe:
tcpSocket:
port: 80
failureThreshold: 3
periodSeconds: 10
readinessProbe:
tcpSocket:
port: 80
failureThreshold: 3
periodSeconds: 10
volumeMounts:
- name: config
mountPath: /config
volumes:
- name: config
persistentVolumeClaim:
claimName: bitwarden-gvolume0
+23
View File
@@ -0,0 +1,23 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: bitwarden
namespace: bitwarden
spec:
ingressClassName: traefik
defaultBackend:
service:
name: bitwarden-vaultwarden-svc
port:
number: 8080
rules:
- host: pm.wittyoneoff.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: bitwarden-vaultwarden-svc
port:
number: 8080
+8
View File
@@ -0,0 +1,8 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- namespace.yaml
- storage.yaml
- deployment.yaml
- service.yaml
- ingress.yaml
+4
View File
@@ -0,0 +1,4 @@
apiVersion: v1
kind: Namespace
metadata:
name: bitwarden
+19
View File
@@ -0,0 +1,19 @@
apiVersion: v1
kind: Service
metadata:
name: bitwarden-vaultwarden-svc
namespace: bitwarden
spec:
type: ClusterIP
selector:
app.kubernetes.io/instance: bitwarden
app.kubernetes.io/name: vaultwarden
ports:
- name: http
port: 8080
targetPort: 80
protocol: TCP
- name: websocket
port: 3012
targetPort: websocket
protocol: TCP
+30
View File
@@ -0,0 +1,30 @@
# GlusterFS-backed volume: /mnt/gvolume0 is the gluster mount present on every node.
apiVersion: v1
kind: PersistentVolume
metadata:
name: bitwarden-pv
spec:
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
- ReadWriteMany
- ReadOnlyMany
persistentVolumeReclaimPolicy: Retain
volumeMode: Filesystem
hostPath:
path: /mnt/gvolume0/bitwarden
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: bitwarden-gvolume0
namespace: bitwarden
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: ""
volumeName: bitwarden-pv