Closed qyk1995 closed 1 year ago
I also encountered this problem. I solved it by:
kubectl -n kube-system get po -o wide
, see whether the csi-attacher-s3-*
and csi-s3-*
are on the same node.
csi.sock
because it doesn't exist on node1.
csi-attacher
kubernetes version: v1.20.6 attacher.yaml image: quay.io/k8scsi/csi-attacher:canary
[root@master01 minio]# kubectl logs pod/csi-attacher-s3-0 -n kube-system I0928 08:59:46.006784 1 main.go:96] Version: v3.1.0-15-g31ad351b W0928 08:59:56.010802 1 connection.go:172] Still connecting to unix:///var/lib/kubelet/plugins/ch.ctrox.csi.s3-driver/csi.sock W0928 09:00:06.010778 1 connection.go:172] Still connecting to unix:///var/lib/kubelet/plugins/ch.ctrox.csi.s3-driver/csi.sock W0928 09:00:16.010769 1 connection.go:172] Still connecting to unix:///var/lib/kubelet/plugins/ch.ctrox.csi.s3-driver/csi.sock W0928 09:00:26.010897 1 connection.go:172] Still connecting to unix:///var/lib/kubelet/plugins/ch.ctrox.csi.s3-driver/csi.sock
What does csi.sock refer to? How to get this file?