Not able to mount volume to csi-app pod about csi-driver-host-path HOT 8 CLOSED

This seems to be the relevant error:

Warning FailedMount 17m (x10 over 21m) kubelet, minikube MountVolume.MountDevice failed for volume "pvc-efb22d61-2728-4e6b-8ed3-cc7554adaaa8" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name hostpath.csi.k8s.io not found in the list of registered CSI drivers

You are deploying on minikube, right? Which version of it? See also #53

from csi-driver-host-path.

@pohly yes,i am using minikube version: v1.7.2

from csi-driver-host-path.

Hi @pohly i am facing issue with v1.7 but later when i deploy csi-hostpath-driver with minikube 1.16 i got succeed in case that csi-app pod got volume mount and while doing so i realise there is step missing of volumesnapshotclass crd i.e while deploying hostpath driver on kubernetes 1.16 volumesnapshotclass not created and we have to explicitly apply it through path csi-driver-host-path/deploy/kubernetes-1.16/snapshotter.So if you don't mind should i modify the docs and add this step.
Thanks
https://github.com/kubernetes-csi/csi-driver-host-path

from csi-driver-host-path.

@Kartik494 i believe you are using 1.17 not 1.7 .

in kubernetes 1.16 snapshot CRD will be created by snapshot sidecar container, that why you are not seeing the issue but in kube 1.17 this is not the case.

as per the csi snapshotter doc distributor's has to bundle and deploy the controller and CRDs as part of their Kubernetes cluster management process

https://github.com/kubernetes-csi/external-snapshotter/blob/release-2.0/README.md#usage

the current host path code here

I think we need to check the CRD's and controller exists or not, if not do we need to create it as part of hostpath driver deployment?

@pohly any suggestions?

from csi-driver-host-path.

@Madhu-1 thanks for suggestion and my concern is when i deployed it in kubernetes 1.16 all crds created but volumesnapshotclass volumesnapshotclass.snapshot.storage.k8s.io/csi-hostpath-snapclass created is not created in my scenario and for volumesnapshotclass we have to explicitly apply yaml which is in path /csi-driver-host-path/deploy/kubernetes-1.16/snapshotter and it is not mention in docs.so i think i should add this step as it has to apply explicitly

from csi-driver-host-path.

I think we need to check the CRD's and controller exists or not, if not do we need to create it as part of hostpath driver deployment?

That would be only a stop-gap solution. As you pointed out, the CRD installation is no longer owned by the driver.

@xing-yang: what do you think?

from csi-driver-host-path.

@Madhu-1 @pohly I will try to clear my situation. The problem has 2 parts:

1. While using k8s version v1.16 , as per the README, I only have to run deploy/kubernetes-1.16/deploy-hostpath.sh to create host-path-driver and get the expected output as mentioned. But the command did not create VolumeSnapshotClass. I had to explicitly apply VolumeSnapshotClass file to get the desired results.
   I am not sure why this is happening. This must either be addressed in the script file or maybe in the main README doc.

2. While using k8s version v1.17, when I ran deploy/kubernetes-1.17/deploy-hostpath.sh I got all the resources (including all beta crd's) installed but I am unable to create Volume object (got error as mentioned initially) while appying my-csi-app. I want some help with this.

As always please tell If something does not make sense. I would be happy to explain it further. Thanks

from csi-driver-host-path.

Hi i am closing this issue as i got the result as volume mount successful.
Thanks

from csi-driver-host-path.