forust
d85bdf5dbd
ci / Compose (pull_request) Successful in 27s
ci / Workflows (pull_request) Successful in 14s
ci / Shell (pull_request) Successful in 34s
ci / Python and tests (pull_request) Successful in 19s
ci / YAML (pull_request) Successful in 17s
ci / Dockerfiles (pull_request) Successful in 6s
ci / Formatting (pull_request) Successful in 36s
ci / Kubernetes (pull_request) Successful in 14s
ci / image-plan (pull_request) Skipped
ci / Image (${{ matrix.name }}) (pull_request) Skipped
ci / build (pull_request) Skipped
renovate-ci / validate-renovate (pull_request_target) Successful in 3m13s
Vaultwarden
Password vault server with persistent data and public/internal ingress.
Kubernetes uses vaultwarden-pvc and the public URL from a ConfigMap.
Compose has a separate data volume. Preserve the database, attachments, and keys
as part of the same backup.
The env example only sets DOMAIN; there is no tracked administrator Secret
example. Configure any administrator token separately and keep it out of Git. Verify
sign-in and client synchronization after any update. Do not use a successful
container restart as the only restore check.
Inspect
From the repository root:
kubectl get pods,svc,pvc -n vaultwarden
kubectl get events -n vaultwarden --sort-by=.metadata.creationTimestamp
See the repository README for deployment selection.