Official Helm charts

[ProbstDJakob]

We as the IT of the computer science department of the university of applied science Darmstadt (Germany) are interested into deploying vaultwarden, but as of now the project lacks an official Helm chart which makes it hard to rollout a productive enterprise level deployment. The wiki currently states two projects which are both unmaintained for 3 years. There is a another repo which is not named (as far as I can tell) anywhere in this repo, but this has some opinionated defaults in regards of the underlying kubernetes cluster (though this my opinion). More importantly this is an unrelated repository and thus does not enjoy the same level of trust as vaultwarden itself and there is no guarantee that the project will live on and always stay up to date with vaultwarden.

We would like to see an officially maintained Helm chart and would be happy to help with that. I have written many helm charts (most of them for internal use but also some for the public) and I also am very familiar with rust, thus I can help with making vaultwarden HA capable.

[sgissi]

Hi @ProbstDJakob, I'm the maintainer of https://github.com/gissilabs/charts/tree/master/vaultwarden. It has been updated quite regularly actually. Back when I started the chart, most Helm charts were in 3rd party repos like Bitnami, but nowadays, official charts are getting more and more common. I would be happy to contribute mine and keep maintaining it under this Github repo/org if the Vaultwarden team prefers. @BlackDex / @dani-garcia, your thoughts?

[sgissi]

I can help with making vaultwarden HA capable

I believe the only issue running multiple Vaultwarden pods/instances is that notifications are sent directly by the instance to the client, and the client might not be connected to the particular instance that is sending the notification back. Otherwise, everything goes through the database. Reference: #2691