Skip to content
DnsLister Forum

Where domain hunters compare notes

Trying to deploy Vaultwarden in k3s with issues

I'm trying to deploy Vaultwarden in my k3s cluster, and it's mostly working…except the service and ingress. The app is running, but it is totally inaccessible. I'm not sure whether I need to use my DeSEC subdomain or whether I can use a .internal fake domain and access it over VPN.

This is the relevant part of my code:

apiVersion: apps/v1 kind: Deployment metadata: name: vaultwarden namespace: vaultwarden labels: app: vaultwarden spec: replicas: 1 selector: matchLabels: app: vaultwarden strategy: type: Recreate template: metadata: labels: app: vaultwarden spec: restartPolicy: Always containers: - name: vaultwarden image: vaultwarden/server:latest env: - name: DOMAIN value: http://vaultwarden.mafmanhomelab.dedyn.io ports: - containerPort: 80 protocol: TCP volumeMounts: - mountPath: /data name: vaultwarden-claim0 volumes: - name: vaultwarden-claim0 persistentVolumeClaim: claimName: vaultwarden-claim0 apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: vaultwarden namespace: vaultwarden labels: app: vaultwarden spec: rules: - host: "vaultwarden.mafmanhomelab.dedyn.io" http: paths: - path: "/" pathType: Prefix backend: service: name: vaultwarden port: number: 8000 apiVersion: v1 kind: Service metadata: name: vaultwarden namespace: vaultwarden labels: app: vaultwarden spec: selector: app: vaultwarden ports: - name: "http" port: 8000 targetPort: 8000 

Source: r/vaultwarden · by /u/ferriematthew

Leave a Reply

Your email address will not be published. Required fields are marked *