Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Use a Deployment when using external database? #4

Closed
rgl opened this issue Jul 11, 2022 · 3 comments · Fixed by #59
Closed

Question: Use a Deployment when using external database? #4

rgl opened this issue Jul 11, 2022 · 3 comments · Fixed by #59

Comments

@rgl
Copy link

rgl commented Jul 11, 2022

Does it make sense to use a Deployment instead of a StatefulSet when using an external database like PostgreSQL?

When using an external database there is no need for the vaultwarden-data volume correct?

@rgl rgl changed the title Question: Use a ReplicaSet when using external database? Question: Use a Deployment when using external database? Jul 11, 2022
@derritter88
Copy link

@rgl
Just installed this Vaultwarden Kubernetes and added it to my existing PostgreSQL cluster.
As far as I can see there is a separate attachements table where it stores the attachements.

I am running it without any additinal volume within Kubernetes.

@guerzon
Copy link
Owner

guerzon commented Jun 9, 2023

Hello @rgl, thanks for raising this question. As explained by @derritter88, Vaultwarden requires the (customizable) /data directory for persistent data such as attachments and icons cache. Ref: https://github.com/dani-garcia/vaultwarden/wiki/Changing-persistent-data-location.

There is at least 1 discussion on object storage, so let's hope such a feature gets implemented soon.

@guerzon guerzon closed this as completed Jun 9, 2023
@guerzon guerzon reopened this Jun 9, 2023
@guerzon
Copy link
Owner

guerzon commented Jun 9, 2023

Having said that, you might get away with using a Deployment + PVC + external DB. Let me test this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants