Yes that's fine. I was able to resolve it by using the "weave net" network on k8s instead of Flannel. For this i had to reinstall the environment (thanks for Florian C). This can be added in the documentation - that we require a specific pod network. Also i didn't see the step for 'kubectl create namespace test' which is required to run the tests as they are in the test namespace.   Anjan
After running the install.isilon, I see that the pods in isilon-controller-0 keeps restarting and then finally goes into crashloopbackoff: [root[NAME] helm]# kubectl get pods -ANAMESPACE NAME READY STATUS RESTARTS AGEisilon isilon-controller-0 2/4 CrashLoopBackOff 12 16misilon isilon-node-4bxgl 2/2 Running 0 16mkube-system coredns-584795fc57-78wgr 1/1 Running 8 2d22hkube-system coredns-584795fc57-7cfkt 1/1 Running 9 2d22hkube-system etcd-localhost.localdomain 1/1 Running 5 2d22hkube-system kube-apiserver-localhost.localdomain 1/1 Running 5 2d21hkube-system kube-controller-manager-localhost.localdomain 1/1 Running 6 2d21hkube-system kube-flannel-ds-amd64-jnvgh 1/1 Running 6 2d22hkube-system kube-proxy-7zpkf 1/1 Running 5 2d22hkube-system kube-scheduler-localhost.localdomain 1/1 Running 6 2d21hkube-system tiller-deploy-586965d498-q6wln 1/1 Running 3 2d21h Looking at the logs i see following errors -  [root[NAME] helm]# kubectl logs -f isilon-controller-0 -n isilon provisionerI1216 17:40:32.391524 1 feature_gate.go:226] feature gates: &{map[]}I1216 17:40:32.391584 1 csi-provisioner.go:98] Version: v1.2.1-0-g971feacbI1216 17:40:32.391594 1 csi-provisioner.go:112] Building kube configs for running in cluster...I1216 17:40:32.398031 1 connection.go:151] Connecting to unix:///var/run/csi/csi.sockW1216 17:40:42.398876 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sockW1216 17:40:52.399053 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sockE1216 17:40:53.400371 1 connection.go:129] Lost connection to unix:///var/run/csi/csi.sock.F1216 17:40:53.400470 1 connection.go:91] Lost connection to CSI driver, exiting [root[NAME] helm]# kubectl logs -f isilon-controller-0 -n isilon attacherI1216 17:38:44.424424 1 main.go:91] Version: v1.1.1-0-g0d83c92I1216 17:38:44.425497 1 connection.go:151] Connecting to unix:///var/run/csi/csi.sockW1216 17:38:54.425740 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sockW1216 17:39:04.425755 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sockE1216 17:39:06.234790 1 connection.go:129] Lost connection to unix:///var/run/csi/csi.sock.W1216 17:39:14.426026 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sockW1216 17:39:24.426267 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sockE1216 17:39:27.273596 1 connection.go:129] Lost connection to unix:///var/run/csi/csi.sock.W1216 17:39:34.426565 1 connection.go:170] Still connecting to unix:///var/run/csi/csi.sock I tried deleting the csi.sock, and reinstalling the driver (helm purge isilon) but come back to this issue. I see the container image gets downloaded successfully but can't figure out this portion: Events:Type Reason Age From Message---- ------ ---- ---- -------Normal Scheduled 3m55s default-scheduler Successfully assigned isilon/isilon-controller-0 to localhost.localdomainNormal Pulled 3m54s kubelet, localhost.localdomain Container image "quay.io/k8scsi/csi-attacher:v1.1.1" already present on machineNormal Created 3m54s kubelet, localhost.localdomain Created container attacherNormal Started 3m54s kubelet, localhost.localdomain Started container attacherNormal Pulling 3m54s kubelet, localhost.localdomain Pulling image "dellemc/csi-isilon:v1.0.0"Normal Started 3m54s kubelet, localhost.localdomain Started container snapshotterNormal Created 3m54s kubelet, localhost.localdomain Created container snapshotterNormal Pulling 3m54s kubelet, localhost.localdomain Pulling image "quay.io/k8scsi/csi-snapshotter:v1.2.0"Normal Pulled 3m54s kubelet, localhost.localdomain Successfully pulled image "quay.io/k8scsi/csi-snapshotter:v1.2.0"Normal Pulled 3m53s kubelet, localhost.localdomain Successfully pulled image "dellemc/csi-isilon:v1.0.0"Normal Created 3m53s kubelet, localhost.localdomain Created container driverNormal Started 3m53s kubelet, localhost.localdomain Started container driverNormal Started 2m55s (x3 over 3m54s) kubelet, localhost.localdomain Started container provisionerWarning BackOff 2m20s (x3 over 3m11s) kubelet, localhost.localdomain Back-off restarting failed containerNormal Created 2m6s (x4 over 3m54s) kubelet, localhost.localdomain Created container provisionerNormal Pulled 2m6s (x4 over 3m54s) kubelet, localhost.localdomain Container image "quay.io/k8scsi/csi-provisioner:v1.2.1" already present on machine   Any ideas?              
csi-isilon: isilon-controller-0 pods in crashloopbackoff