[Feature]: Statefulset vs Deployment

[Munsio]

Feature Description

Usually in Kubernetes deployments are used to deploy stateless applications, if an PVC is involved it has to be an "ReadWriteMany" one so all deployments can access it.

This is especially needed with the default "RollingUpdate" strategy of an deployment.

In case of the deployments within this Repo they are all defined with a config PVC which is explicitly set to "ReadWriteOnce" so only 1 pod is able to access the PVC at any given time.

The problem that I am facing a few versions since now is that when trying to deploy a new version the Pods won't start because of an "Multi-Attach" error on the config PVC.

A workaround would be to set the "Strategy" to "Recreate" instead of "RollingUpdate" but then per definition it would be better to use a Stateful set anyway.

I want to have your Input on this topic. As a first workaround we could switch to "Recreate" so updating is without any pain but I guess the end goal would be to switch to a Stateful set anyway as the applications the Charts are for are designed to be stateful itself.