fix doc about csi socket path

Signed-off-by: Patrik Cyvoct <[email protected]>

README.md

@@ -36,9 +36,9 @@ There are two UNIX domain sockets used by the node-driver-registrar:
 * CSI driver socket:
   * Used by kubelet to interact with the CSI driver.
   * Created by the CSI driver.
-  * Exposed on a Kubernetes node via hostpath somewhere other than the Kubelet.
-    plugin registry (typically `/var/lib/kubelet/plugins/<drivername.example.com>/csi.sock`).
+  * Exposed on a Kubernetes node via hostpath somewhere other than the Kubelet plugin registry. (typically `/var/lib/kubelet/csi-plugins/<drivername.example.com>/csi.sock`).
   * This is the socket referenced by the `--csi-address` and `--kubelet-registration-path` arguments.
+  * Note that if the csi socket is in the `/var/lib/kubelet/plugins/` path, kubelet may log a lot of harmful errors regarding grpc `GetInfo` call not implemented (see kubernetes/kubernetes#70485)
 
 ### Required arguments
 
@@ -58,7 +58,7 @@ rules are needed.
 It does, however, need to be able to mount hostPath volumes and have the file
 permissions to:
 
-* Access the CSI driver socket (typically in `/var/lib/kubelet/plugins/<drivername.example.com>/`).
+* Access the CSI driver socket (typically in `/var/lib/kubelet/csi-plugins/<drivername.example.com>/`).
   * Used by the `node-driver-registrar` to fetch the driver name from the driver
     contain (via the CSI `GetPluginInfo()` call).
 * Access the registration socket (typically in `/var/lib/kubelet/plugins_registry/`).
@@ -92,7 +92,7 @@ the actual driver's name.
             type: Directory
         - name: plugin-dir
           hostPath:
-            path: /var/lib/kubelet/plugins/<drivername.example.com>/
+            path: /var/lib/kubelet/csi-plugins/<drivername.example.com>/
             type: DirectoryOrCreate
 ```