Closed tgates-nalej closed 3 years ago
I got a very similiar situation, only one pvc increased to 10G and other 2 stay in 200m. By the way how did you get the error message?
Thank you. There is an issue #34 which was reported from a user with a similar issue.
It seems like expanding the storage does not work as expected in all use-cases.
I am going to work on this potential bug fix next.
I am closing this issue and you can follow an update by watching #34
I committed a potential bug fix in master.
To test it, please run the following command in your Kubernetes cluster:
kubectl apply -f https://raw.githubusercontent.com/reactive-tech/kubegres/main/kubegres.yaml
Could you please help me by testing it and let me know if you are happy with it?
Once you confirmed it is working for you, I will create a new tag 1.10
Please let me know and thanks in advance for your help!
I am following the getting started example, using an expandable K8s StorageClass on AWS:
I created the Kubegres cluster with the following:
I then created a database, table, and inserted some rows into it.
Then I edited the Kubegres CR, changing
spec.database.size
from200Mi
to10Gi
.The Kubegres operator then resized the PVC for
postgres-db-mypostgres-3-0
to be10Gi
:And then it failed with a timeout error:
The
status
of the Kubegres CR shows:How do I recover from this scenario?