i install k8s-csi-s3 successfully in hosted k8s, and i mount a minio prefix into pod using static pv successfully.

but one day, the container in pod was killed because linux oom killer, the exist code is 137.

and you know, k8s try restarting the container itself, but the container status continuously waiting, please see below image.

when i delete pod, the restart pod, everything going well. so what's the root cause?

the logs:
failed to generate container "16aa862fb1ba30683d5e321bae3ccf177dc55c1ae81a41b824ca2395f0a4b1eb" spec: failed to generate spec: failed to stat "/var/lib/kubelet/pods/2219aa68-92ca-4535-bc87-84a39bb9cb83/volumes/kubernetes.io~csi/jupyterlab-pv-13784056164704/mount": stat /var/lib/kubelet/pods/2219aa68-92ca-4535-bc87-84a39bb9cb83/volumes/kubernetes.io~csi/jupyterlab-pv-13784056164704/mount: transport endpoint is not connected