GRPC error: Timeout waiting for mount

[Talavig]

We have tried to install the csi-s3 suite on out test cluster, it seems to have deployed successfully, we have statically created a pv and a pvc to map to a specific bucket as shown in the documentation, and the mount fails with the message in the issue's title.
It's important to note that we are running in an air gapped environment, with no support for outer cluster GRPC communication, but we have not found a way to change it to http if such thing is even possible. Is there any workaround that can help us with it? Or is the grpc communication a must?
Thanks in advance:)

[vitalif]

Hi I'm not sure what you mean by outer cluster GRPC communication... csi-s3 itself doesn't use grpc access to k8s installation, CSI sidecars of course do it.
Maybe you have a problem with systemd "escaping from container" method? Then you can try to add --no-systemd to mount options (see README).
Or maybe you have a problem with custom kubelet path? Current charts use /var/lib/kubelet by default (it can be changed via Helm).
Also please check logs of csi-s3 containers, maybe it will give you a hint about what's wrong.