You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used a recent version of the operator from master. The change of the requested size is read without SI suffix. So, the change from 300Gi -> 350Gi results in some strange storage request size of 350.
This is confirmed, using value in bytes correctly resize the volume (without data lost).
@jkrajniak , we use Si-suffixed PVCs everywhere, including oci Kubernetes. I wonder how did you change the PVC?
So the first deployment of the cluster with Si-suffixes works correctly. Only when I tried to resize (fortunately on my some dev cluster instance) with the value also with suffix, this failes. I have k8s version: v1.22.5;
I haven't check in general how the OCI cluster in this version behaves for other PVC during the resize - maybe that's not the issue with Clickhouse operator but rather with the OCI K8s.
I have used a recent version of the operator from master. The change of the requested size is read without SI suffix. So, the change from
300Gi
->350Gi
results in some strange storage request size of350
.This is confirmed, using value in bytes correctly resize the volume (without data lost).
Originally posted by @jkrajniak in #1263 (comment)
The text was updated successfully, but these errors were encountered: