If the kubelet working directory in the cluster is different，how to use node-driver-registrar

[sys-liqian]

in my kubernetes cluster
node1 kubelet woring dir is /var/lib/kubelet
node2 kubelet woring dir is /data/kubelet
how do i use node-driver-registrar

[mauriciopoppe]

Sorry for the late response, while we have these paths exposed as cli args I don't think we tested by having the kubelet working dir different to /var/lib/kubelet.

I'm not sure if the following will work:

      containers:
        - name: csi-driver-registrar
          image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0
          args:
            - "--csi-address=/csi/csi.sock"
            - "--kubelet-registration-path=/var/lib/kubelet/plugins/<drivername.example.com>/csi.sock"
            - "--health-port=9809"
          volumeMounts:
            - name: plugin-dir
              mountPath: /csi
            - name: registration-dir
              mountPath: /registration
          ports:
            - containerPort: 9809
              name: healthz
          livenessProbe:
            httpGet:
              path: /healthz
              port: healthz
            initialDelaySeconds: 5
            timeoutSeconds: 5
      volumes:
        - name: registration-dir
          hostPath:
            path: /data/kubelet/plugins_registry/
            type: Directory
        - name: plugin-dir
          hostPath:
            path: /data/kubelet/plugins/<drivername.example.com>/
            type: DirectoryOrCreate

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mauriciopoppe]

Feel free to reopen this issue if your problem wasn't solved by #207 (comment)