Deploy Vaultwarden instance as a Deployment instead of StatefulSet
Thank you for providing the K8s Helm chart for the Vaultwarden, it's really convenient to deploy it using a ready-to-use chart rather than manually!
But I see that it deploys the Vaultwarden instance as a StatefulSet, but from my point of view - it's more correct to run it just as a Deployment. It's because it uses the remote database connection, and the persistence for the config and attachments should used as a shared volume, not as a separate volume per instance.
Considering this, deploying as a Deployment looks more correct.
And with the accessMode: ReadWriteMany
we can run even several instances of the Vaultwarden Deployment reusing the same volume, with load balancer.
To not break the previous deployment, we can introduce an option to deploy it as a Deployment instead of a StatefulSet.
What do you think about this idea?