1
0
Fork 0
kubernetes/updatebot
Dustin 94be854bd7 vaultwarden: Deploy, migrate Vaultwarden
Vaultwarden requires basically no configuration anymore.  Older versions
needed some environment variables for configuring the WebSocket server,
but as of 1.31, WebSockets are handled by the same server as HTTP, so
even that is not necessary now.  The only other option that could
potentially be useful is `ADMIN_TOKEN`, but it's optional.  For added
security, we can leave it unset, which disables the administration
console; we can set it later if/when we actually need that feature.

Migrating data from the old server was pretty simple.  The database is
pretty small, and even the attachments and site icons don't take up much
space.  All-in-all, there was only about 20 MB to move, so the copy only
took a few seconds.

Aside from moving the Vaultwarden server itself, we will also need to
adjust the HAProxy configuration to proxy requests to the Kubernetes
ingress controller.
2025-01-10 20:05:18 -06:00
..
.gitignore updatebot: Add CronJob to run for Home Assistant 2024-08-27 18:05:50 -05:00
config.yml vaultwarden: Deploy, migrate Vaultwarden 2025-01-10 20:05:18 -06:00
kustomization.yaml updatebot: Updates for latest version 2024-09-08 19:54:58 -05:00
namespace.yaml updatebot: Add CronJob to run for Home Assistant 2024-08-27 18:05:50 -05:00
rbac.yaml updatebot: Updates for latest version 2024-09-08 19:54:58 -05:00
secrets.yaml updatebot: Add CronJob to run for Home Assistant 2024-08-27 18:05:50 -05:00
ssh_known_hosts updatebot: Add CronJob to run for Home Assistant 2024-08-27 18:05:50 -05:00
sshkey.pub updatebot: Add CronJob to run for Home Assistant 2024-08-27 18:05:50 -05:00
updatebot.yaml updatebot: Schedule updats on Saturday morning 2024-09-22 11:53:52 -05:00