nmaupu / freenas-provisioner

Kubernetes external provisioner using Freenas as backend

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

status 404 Sorry, this request could not be processed. Please try again later

lzhengqc opened this issue · comments

After run kubectl apply -f deploy\test-claim.yaml, pvc is in pending status.

Log message from pvc shows following

failed to provision volume with StorageClass "freenas-nfs": Error getting dataset "tank" - message: {"error_message":"Sorry, this request could not be processed. Please try again later."}, status: 404

This project is in maintenance mode. If you're just getting started I suggest you head over here: https://github.com/democratic-csi/charts/tree/master/stable/democratic-csi/examples

It's not been fully documented yet but if you want to open an issue over there I'm happy to help out and make sure we get you going.

This project is in maintenance mode.

Hum, no, it's not. I am still using it and there is no other alternative for now to provision without having to require an ssh access to a freenas box and use yours... I will migrate to CSI when I get the chance.

@nmaupu ok, sorry my friend. DIdn't realize you intended to carry forward with this trying to convert it to csi (it's nearly impossible to implement a 'migration' path FYI without some major headache). I'd recommend starting a new project if you don't want to use democratic-csi.

I can share some gory details sometime if you want to get an idea what you're up against.

It would be possible to create an HTTP only adapter to the other project in theory as well if you wanted to discuss that.

I'd be interested in knowing/understanding the aversion to ssh.