madhur-df

@sourabhaggrawal What was the issue with keeper nodes and how did you fix it?

@Slach yes I have `allowVolumeExpansion: true` in the storage class. Also, like I said, the issue is about upgrading storage. When I do that, the storage indeed gets upgraded but...

``` NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE gp2 (default) kubernetes.io/aws-ebs Delete WaitForFirstConsumer true 4y135d ``` and on describing, I get this: ``` Name: gp2 IsDefaultClass: Yes Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"},"name":"gp2"},"parameters":{"fsType":"ext4","type":"gp2"},"provisioner":"kubernetes.io/aws-ebs","volumeBindingMode":"WaitForFirstConsumer"} ,storageclass.kubernetes.io/is-default-class=true Provisioner:...

> kubectl get chi --all-namespaces ``` NAMESPACE NAME CLUSTERS HOSTS STATUS HOSTS-COMPLETED AGE logging ch-installation 1 6 Completed 5d21h ``` > kubectl get pod --all-namespaces -l app=clickhouse-operator ``` NAMESPACE NAME...

Unfortunately, I am still facing this issue. I upgraded storage from 300Gi to 500Gi and I was using 3 shards and 2 replicas with zookeeper. All my existing data was...