Hi Shashikant,

There is not enough information here to determine the cause. Please check the pod description and container logs for further details.

Describe commands:

kubectl describe deployment/csi-smb-controller -n ifs-storage
kubectl describe daemonset/csi-smb-node -n ifs-storage

Get the logs for each container. (Note: each pod contains three containers.):

kubectl logs deployment/csi-smb-controller -c csi-provisioner -n ifs-storage
kubectl logs deployment/csi-smb-controller -c smb -n ifs-storage
kubectl logs deployment/csi-smb-controller -c liveness-probe -n ifs-storage
kubectl logs daemonset/csi-smb-node -c smb -n ifs-storage
kubectl logs daemonset/csi-smb-node -c node-driver-registrar -n ifs-storage
kubectl logs daemonset/csi-smb-node -c liveness-probe -n ifs-storage

Depending on when the pods crash, you may also append -p to the above output to try to get the logs for the previously crashed pods.

Best regards -- Ben

Hi,

Issue has been resolved after run 

.\main.ps1 -resource 'CHANGE-POD-IP-RANGE'

Thanks

Sashikant