# vsphere


01/16/2023, 8:54 PM
Hello, we have a cluster deployed, k8s 1.22, when we are trying to make use of the vsphere CSI controller, we kept getting an i/o timeout when connecting to vsphere and the only way around it was to add our name server to the k8s netpol, obviously we dont want to do that, we deployed another test pod using the exact same netpol however we excluded the name server and it worked fine. We noticed that dnsPolicy on the vsphere CSI controller is Default, we updated that too ClusterFirst and could see the connection working as expected, however now the pods keep going into. CrashLoopBackoff with the following error: Still connecting to <unix///csi/csi.sock|unix///csi/csi.sock> Any ideas?