I have find out the actual problem was firewall related. After I done the follow command, everything worked as expect.
Dear All: I deploy a k8s cluster with 1 master and 1 worker. I've done all installation requirement from the installation guide as below. When I try to test the sample.yaml from csi driver package, everything does now work correctly [URL] Here is the environment info: K8s version: 1.22.0 CSI Driver version: 2.22.0 The output related to sample.yaml [root[NAME]-master-1 ~]# kubectl get all -n test-unityNAME READY STATUS RESTARTS AGEpod/unitytest-0 0/1 Pending 0 45m NAME READY AGEstatefulset.apps/unitytest 0/1 45m [root[NAME]-master-1 ~]# kubectl get pvc -n test-unityNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEpvol1 Pending unity-virt2212drzmzg-iscsi 46mpvol2 Pending unity-virt2212drzmzg-nfs 46m I only test iSCSI and NFS, so only 2 pvc were list [root[NAME]-master-1 ~]# kubectl describe -n test-unity pvc/pvol1Name: pvol1Namespace: test-unityStorageClass: unity-virt2212drzmzg-iscsiStatus: PendingVolume:Labels: Annotations: volume.beta.kubernetes.io/storage-provisioner: csi-unity.dellemc.com Finalizers: [kubernetes.io/pvc-protection] Capacity: Access Modes: VolumeMode: Filesystem Used By: unitytest-0 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ExternalProvisioning 2m14s (x181 over 47m) persistentvolume-controller waiting for a volume to be created, either by external provisioner "csi-unity.dellemc.com" or manually created by system administrator  [root[NAME]-master-1 ~]# kubectl describe -n test-unity pvc/pvol2Name: pvol2Namespace: test-unityStorageClass: unity-virt2212drzmzg-nfsStatus: PendingVolume:Labels: Annotations: volume.beta.kubernetes.io/storage-provisioner: csi-unity.dellemc.com Finalizers: [kubernetes.io/pvc-protection] Capacity: Access Modes: VolumeMode: Filesystem Used By: unitytest-0 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ExternalProvisioning 2m32s (x181 over 47m) persistentvolume-controller waiting for a volume to be created, either by external provisioner "csi-unity.dellemc.com" or manually created by system administrator  PVC create were stock in pending state, waiting for volume create.... No PV were created [root[NAME]-master-1 ~]# kubectl get pvNo resources found The controller driver log is as below [root[NAME]-master-1 ~]# kubectl logs -n unity unity-controller-65475c6457-dkhdq -c driverEndpoint /var/run/csi/csi.sockI0414 07:45:44.600881 1 leaderelection.go:243] attempting to acquire leader lease unity/driver-csi-unity-dellemc-com...E0414 07:46:14.602401 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:46:53.231553 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:47:33.879394 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:48:12.870109 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:48:50.497694 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:49:28.049399 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:50:07.175095 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeoutE0414 07:50:42.570874 1 leaderelection.go:325] error retrieving resource lock unity/driver-csi-unity-dellemc-com: Get "[URL]": dial tcp 10.96.0.1:443: i/o timeout I found 10.96.0.1 was Kubernetes cluster IP, but why the controller show all this message. Does anyone can help me to find out the problem? Best Regards,  
Unity CSI Driver failed