Re: CSI NFS driver error message No such image: quay.io/k8scsi/nfsplugin:v0.3.0

[Saad Ali]

Hi Mike,

The NFS driver and images do need to be updated. Unfortunately we have no volunteer maintaining it at the moment.

SIG Storage is looking for an owner for the CSI NFS driver. Someone who is willing to:

1. Move the NFS CSI driver code from https://github.com/kubernetes-csi/drivers/tree/master/pkg/nfs to https://github.com/kubernetes-csi/csi-driver-nfs
2. Update the driver to be CSI 1.0 compatible.
   
3. Cut new 0.x and 1.x branches and images of the driver.

If you or someone you know is interested, please let me know.

On Sat, Feb 2, 2019 at 6:35 AM <mike...@gmail.com> wrote:

I am trying out the CSI NFS driver https://github.com/kubernetes-csi/drivers/tree/master/pkg/nfs at from instructions in web links of https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.1/manage_cluster/using_csi.html and https://medium.com/ibm-cloud/using-csi-in-ibm-cloud-private-5212d6bf2ae3 in my test environment.

Downloaded from https://github.com/kubernetes-csi/drivers the file drivers-master.zip and extracted onto Kubernetes master node where I installed NFS V4 server as well to test the CSI NFS driver in my test environment.

kubectl create -f ./deploy/kubernetes/
service/csi-attacher-nfsplugin created
statefulset.apps/csi-attacher-nfsplugin created
serviceaccount/csi-attacher created
clusterrole.rbac.authorization.k8s.io/external-attacher-runner created
clusterrolebinding.rbac.authorization.k8s.io/csi-attacher-role created
daemonset.apps/csi-nodeplugin-nfsplugin created
serviceaccount/csi-nodeplugin created
clusterrole.rbac.authorization.k8s.io/csi-nodeplugin created
clusterrolebinding.rbac.authorization.k8s.io/csi-nodeplugin created

kubectl get pods
NAME                             READY   STATUS             RESTARTS   AGE
csi-attacher-nfsplugin-0         0/2     CrashLoopBackOff   13         58m
csi-nodeplugin-nfsplugin-7kfdz   0/2     CrashLoopBackOff   13         58m
csi-nodeplugin-nfsplugin-pnrwq   0/2     CrashLoopBackOff   13         58m

journalctl shows repeated messages below.

Feb 02 09:00:20 crhel7 dockerd-current[8452]: time="2019-02-02T09:00:20.738671041-05:00" level=error msg="Handler for GET /v1.26/images/quay.io/k8scsi/nfsplugin:v0.3.0/json returned error: No such image: quay.io/k8scsi/nfsplugin:v0.3.0"

File csi-attacher-nfsplugin.yaml contains image: quay.io/k8scsi/nfsplugin:v0.3.0

https://quay.io/repository/k8scsi/nfsplugin?tab=tags shows only version v0.2.0 of image. There is no v0.3.0 of image for quay.io/k8scsi/nfsplugin:v0.3.0.

Quay Security Scanner has detected 31 vulnerabilities with 31 RHSA Patches are available for 31 vulnerabilities. 

Will there be a new Docker image create for quay.io/k8scsi/nfsplugin that is most recent CSI NFS driver code and installation of all the current RHSA security vulnerability packages?

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-storage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-st...@googlegroups.com.
To post to this group, send email to kubernetes-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-storage/c82da9b5-8dd5-449f-88d7-bd53c39fe8f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mathusan Selvarajah]

Hi Saad,

I think I can help maintain the CSI NFS driver. I've had experience using it, and know that there are some issues that need to be fixed.

Mathusan

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-storage/CABBBJP03aapvayG9e0M%3DEwHud8zfZ7AEADxc7m4BTKd_7KthOQ%40mail.gmail.com.