minio operator helm deploy on k8s, request a large amount of memory (14G), modify to 4G and cannot be started

[wangchao732]

minio operator: 'minio/operator:v5.0.7'

When I forcibly delete the pod, it shows that it will automatically initialize and create a new pod, but the result is unexpected, and it keeps re-initializing because the directory cannot be mounted. But persistent volumes exist, so why can't they be mounted?

1710732090642

Errorlog:

47211 kubelet.go:1761] "Unable to attach or mount volumes for pod; skipping pod" err="unmounted volumes=[data2 data3 data0 data1], unattached volumes=[data2 data3 cfg-vol configuration kube-api-access-j9xbj data0 data1]: timed out waiing for the condition" pod="tenantns/filestore-pool-0-3"
pod_workers.go:951]"Error syncing pod, skipping" err="unmounted volumes=[data2 data3 data0 data1], unattached volumes=[data2 data3 cfg-vol configuration kube-api-access-j9xbj data0 data1]: timed out waiting for the condition" pod="tenantns/filestore-pool-0-3" podUID=e4325f61-a5fb-4f5d-9c8b-22c7faf071a4

What am I going to do?