Closed Destreyf closed 2 years ago
Ignore this, I didn't realize that when i tore down the services the volumes remained, so my original deployment attempt had left existing volumes there, once I removed the original failed volumes they were re-provisioned correctly.
Name and Version
bitnami/postgres-ha:9.2.4
What steps will reproduce the bug?
Set persistence.size to 20Gi and install the helm chart.
I've tested with a values.yaml and --set and neither work.
Are you using any custom parameters or values?
and tried
--set persistence.size=20Gi
What is the expected behavior?
Volume claim should use specified size, in this case it should be 20 Gigabytes.
What do you see instead?
Instance requests an 8Gi PVC which does not work on vultr (they have a 10 Gig minimum)
Additional information
I am using Vultr's VKE environment and they have a minimum nvme block size of 10 gigabytes, and a minimum hdd block size of 40 gigabytes.