I really welcome the removal of the bitnami postgresql chart because this provides to possibility to simplifies dependencies and provides a better control perspective. Unfortunately the current implementation does not provide the possibility to configure postgresql in detail.
For us the most problematic thing is, that we cannot configure memory/buffer related settings of postgresql with the current implementation. Therefore the current implementation is not ready for production due to the fact that we ran a postgresql instance with several dozens of gigabytes.
Version of Helm and Kubernetes:
-/-
What happened:
-/-
What you expected to happen:
Be capable to configure all postgresql settings.
How to reproduce it (as minimally and precisely as possible):
Describe the bug
I really welcome the removal of the bitnami postgresql chart because this provides to possibility to simplifies dependencies and provides a better control perspective. Unfortunately the current implementation does not provide the possibility to configure postgresql in detail. For us the most problematic thing is, that we cannot configure memory/buffer related settings of postgresql with the current implementation. Therefore the current implementation is not ready for production due to the fact that we ran a postgresql instance with several dozens of gigabytes.
Version of Helm and Kubernetes: -/-
What happened: -/-
What you expected to happen:
Be capable to configure all postgresql settings.
How to reproduce it (as minimally and precisely as possible):
Use a real world production setup.
Anything else we need to know: -/-