What is the official/conventional way of creating the volumes in a CSI plugin?

[mbtamuli]

Goal

• Find out what is the official/conventional way to create the volumes
  • same volume as CSI
  • separate volume

Background

Ref: #25 (comment)

• A volume mounted from the host in both the plugin container and the node-driver-registrar container, which is used primarily for the CSI socket

  spec:
    template:
      spec:
        containers:
          - volumeMounts:
              - mountPath: /csi
                name: plugin-dir
        volumes:
          - hostPath:
              path: /var/lib/kubelet/plugins/emptydirclone.mriyam.dev
              type: DirectoryOrCreate
            name: plugin-dir

• The plugin creating a volume, that gets mounted at the target path as requested by kubelet. Now the path that the plugin uses for creating the volume lives under the path /csi

   // getVolumePath returns the canonical path for emptydirclone volume
   func getVolumePath(volName string) string {
   	return filepath.Join("/csi/data", volName)
   }

Although this works, the pattern I've seen is,

• A volume separate from the one used for the CSI socket mounted from the host in both the plugin container and the node-driver-registrar container

  spec:
    template:
      spec:
        containers:
          - volumeMounts:
            - mountPath: /csi-data-dir
              name: csi-data-dir
      volumes:
        - hostPath:
            path: /var/lib/csi-emptydirclone.mriyam.dev-data/
            type: DirectoryOrCreate
          name: csi-data-dir

• The plugin uses the volume /csi-data-dir/ to create all volumes within that path.