Giter VIP home page Giter VIP logo

Comments (15)

andyzhangx avatar andyzhangx commented on May 20, 2024

just could not find the correct commit:

git checkout 2571bd3ff69187efbaef51f3eae6235af59b1614
root@andy-dev:~/go/src/github.com/kubernetes-csi/drivers# make hostpath
if [ ! -d ./vendor ]; then dep ensure; fi
go build -i -o _output/hostpathplugin ./app/hostpathplugin
# github.com/kubernetes-csi/drivers/pkg/csi-common
pkg/csi-common/utils.go:97:9: cannot use ids (type *DefaultIdentityServer) as type csi.IdentityServer in argument to s.Start:
        *DefaultIdentityServer does not implement csi.IdentityServer (missing GetPluginCapabilities method)
pkg/csi-common/utils.go:105:9: cannot use ids (type *DefaultIdentityServer) as type csi.IdentityServer in argument to s.Start:
        *DefaultIdentityServer does not implement csi.IdentityServer (missing GetPluginCapabilities method)
pkg/csi-common/utils.go:113:9: cannot use ids (type *DefaultIdentityServer) as type csi.IdentityServer in argument to s.Start:
        *DefaultIdentityServer does not implement csi.IdentityServer (missing GetPluginCapabilities method)
Makefile:30: recipe for target 'hostpath' failed

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

v0.1.0 works, while there is build error for master branch

from drivers.

sbezverk avatar sbezverk commented on May 20, 2024

@andyzhangx Currently CSI master points to CSI Spec 0.2.0 which introduced breaking changes. There is an effort to convert all existing plugins, as well as provisioner/attacher/registrar to support CSI Spec 0.2.0. Here is my PR which addresses hostpath plugin and csi-common 0.2.0 changes:
#56
Please keep in mind that you still need new provisioner and registrar. New external attacher was merged this morning.

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

@sbezverk thanks, I am going to write a new CSI driver, so should I start with v0.1.0 or just wait for 0.2.0? I still need new provisioner and registrar for 0.2.0, it looks like v0.2.0 is still on-going.

from drivers.

sbezverk avatar sbezverk commented on May 20, 2024

@andyzhangx please do not bother doing anything for 0.1.0, registrar and attacher are already merged, provisioner will be merged tomorrow. You can start working for 0.2.0 right away :)

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

@sbezverk thanks for clarification, I just would like to make it very detailed, so when the following images would be ready in docker hub, do I need to build them myself?

docker.io/k8scsi/csi-provisioner:0.2
docker.io/k8scsi/csi-attacher:0.2
docker.io/k8scsi/driver-registrar:0.2

Is there any example config when 0.2.0 is ready, I got an 0.1.0 example from here:
https://raw.githubusercontent.com/lpabon/csi-workspace/master/demo/hostPath.yaml

from drivers.

sbezverk avatar sbezverk commented on May 20, 2024

@andyzhangx the images will be available at quay.io/k8scsi
See this link for my hostpath plugin yaml: https://gist.github.com/sbezverk/2229db8d27968c1a968e3a4ab5dabe14

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

@sbezverk thanks, you are awesome!

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

hi @sbezverk you are using image from 192.168.80.240:4000/k8scsi/csi-provisioner:v0.2.0, could you put those images into docker pub? thanks.

from drivers.

arm64b avatar arm64b commented on May 20, 2024

Hello @sbezverk , I've setup an CSI-enabled k8s cluster with kubeadm, but when I create the csi-pod with:

#kubectl create -f https://raw.githubusercontent.com/kubernetes-csi/docs/master/book/src/example/csi-setup.yaml

The command kubectl get pod always shows:

s# kubectl get pod
NAME      READY     STATUS              RESTARTS   AGE
csi-pod   0/4       ContainerCreating   0          3m

Do I need to adapt that yml file to my local environment, but seems there's not env specific settings in that yaml file. Any suggestions?

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

external-provisioner is crahsing, it says:

#kubectl logs -p csi-pod -c external-provisioner
I0315 08:14:04.529371       1 csi-provisioner.go:68] Building kube configs for running in cluster...
I0315 08:14:04.561105       1 controller.go:84] Connecting to /csi/csi.sock
I0315 08:14:04.561319       1 controller.go:111] Still trying, connection is CONNECTING
I0315 08:14:04.561816       1 controller.go:108] Connected
I0315 08:14:04.561879       1 controller.go:75] GRPC call: /csi.v0.Identity/GetPluginCapabilities
I0315 08:14:04.561961       1 controller.go:76] GRPC request:
I0315 08:14:04.564703       1 controller.go:78] GRPC response: capabilities:<service:<> >
I0315 08:14:04.564749       1 controller.go:79] GRPC error: <nil>
F0315 08:14:04.564792       1 controller.go:198] no plugin controller service support detected

from drivers.

arm64b avatar arm64b commented on May 20, 2024

@andyzhangx are you using the cmd #kubectl create -f https://raw.githubusercontent.com/kubernetes-csi/docs/master/book/src/example/csi-setup.yaml to create the csi-pod? But the output of #kubectl logs -p csi-pod -c external-provisioner in my side is:

# kubectl logs -p csi-pod -c external-provisioner
Error from server (BadRequest): previous terminated container "external-provisioner" in pod "csi-pod" not found

from drivers.

andyzhangx avatar andyzhangx commented on May 20, 2024

@arm64b yes, i am using the same cmd, you may delete it and recreate.

from drivers.

arm64b avatar arm64b commented on May 20, 2024

Yes, I delete it, the kubectl get pod shows No resources found, then I create it again with kubectl create -f https://raw.githubusercontent.com/kubernetes-csi/docs/master/book/src/example/csi-setup.yaml:

storageclass "csi-hostpath-sc" created
serviceaccount "csi-service-account" created
clusterrole "csi-cluster-role" created
clusterrolebinding "csi-role-binding" created
pod "csi-pod" created

The kubectl get pod output then:

NAME      READY     STATUS              RESTARTS   AGE
csi-pod   0/4       ContainerCreating   0          3s

After that:

# kubectl logs -p csi-pod -c external-provisioner
Error from server (BadRequest): previous terminated container "external-provisioner" in pod "csi-pod" not found

from drivers.

pohly avatar pohly commented on May 20, 2024

F0315 08:14:04.564792 1 controller.go:198] no plugin controller service support detected

This was found and fixed yesterday, see PR #69. The images need to be updated to reflect that.

from drivers.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.