Allow disabling persistant storage #5081
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Is your feature request related to a problem? Please describe.
I would like to be able to disable the persistant volume so we can use Consul with ephemeral storage instead. In our use case we only use the services catalog. Our services are setup with a lot of resilience in regards to keeping themselves in the consul catalog when healthy.
We ran with the bitnami chart for a while because it didn't use persistant volumes and it ran perfectly.
We also notice that it can take a while for a volume to be re-mounted to the node k8s wants to put the consul pod onto, which is the main reason its a problem for us now that we switched to the official consul helm chart.
Feature Description
Add a config property to disable pvc and use ephemeral storage instead.
Use Case(s)
As mentioned above, some use cases in consul do not require persistant storage thus the option should exist to disable it.
Contributions
I can help setup a pr. I did notice a pr for this already exists but is not linked to an issue, therefor i decided to create the issue. See #3385. I do not know what needs to be done to get that pr merged as to me it looks pretty solid. Please let me know what I need to do to get that merged.