Skip to content

Commit

Permalink
Merge pull request #59 from Sh4d1/fix_doc
Browse files Browse the repository at this point in the history
fix doc about csi socket path
  • Loading branch information
k8s-ci-robot authored Dec 4, 2019
2 parents 204944a + c65f9a7 commit 8f7e0d3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/plugins/<drivername.example.com>/csi.sock`).
* This is the socket referenced by the `--csi-address` and `--kubelet-registration-path` arguments.
* Note that before Kubernetes v1.17, if the csi socket is in the `/var/lib/kubelet/plugins/` path, kubelet may log a lot of harmless errors regarding grpc `GetInfo` call not implemented (fix in kubernetes/kubernetes#84533). The `/var/lib/kubelet/csi-plugins/` path is preferred in Kubernetes versions prior to v1.17.

### Required arguments

Expand Down

0 comments on commit 8f7e0d3

Please sign in to comment.