Is your feature request related to a problem? Please describe.
Utilising persistent volumes makes redeployments slower as the binding for the mount potentially needs to migrate between nodes. This downtime could be reduced by having an emptyDir data volume.
Describe the solution you'd like
Being able to set an emptyDir for the "read" component, analagous to the other components.
Describe alternatives you've considered
Currently we just have a PVC for the "read" component" and emptyDir for the others.
Additional context
It is possible to set an emptyDir as the data volume for the write and backend components in the SimpleScalable deployment mode, but not for the read component. Honestly I'm not sure which of the three components is the one that would most require a persistent volume as the documentation regarding the "statefulness" of the individual components wasn't easy to put together.
Is your feature request related to a problem? Please describe.
Utilising persistent volumes makes redeployments slower as the binding for the mount potentially needs to migrate between nodes. This downtime could be reduced by having an emptyDir data volume.
Describe the solution you'd like
Being able to set an emptyDir for the "read" component, analagous to the other components.
Describe alternatives you've considered
Currently we just have a PVC for the "read" component" and emptyDir for the others.
Additional context
It is possible to set an emptyDir as the data volume for the write and backend components in the SimpleScalable deployment mode, but not for the read component. Honestly I'm not sure which of the three components is the one that would most require a persistent volume as the documentation regarding the "statefulness" of the individual components wasn't easy to put together.