Open andrewchron opened 7 years ago
@andrewchron Unfortunately it seems like Rook is pretty much broken right now. It's probably neither of us' fault, instead I think there's a slight bug in the operator that made it stop working now.
I'll look into it.
@andrewchron and @luxas: I ran into the same issue with rook. I used nfs for persistent volume provisioning as an alternative.
I changed luxas files as follows: https://github.com/Dr-Agonite/rpi-kubernetes/tree/master/demos
Hope this helps.
Another option is to use an older version of rook. Version 0.5.0 supports rook-rook-user.
You need to change one line in rook-operator.yaml before: image: rook/rook:v0.5.1 after: image: rook/rook:v0.5.0
Same applies for rook-cluster.yaml. before: versionTag: v0.5.1 after: versionTag: v0.5.0
rook-storageclass.yaml stays unchanged.
So far so good the workshop, however when i run the command kubectl get secret rook-rook-user -oyaml | sed "/resourceVer/d;/uid/d;/self/d;/creat/d;/namespace/d" | kubectl -n kube-system apply -f -
I get as a response
-Error from server (NotFound): secrets "rook-rook-user" not found error: no objects passed to apply
Is it something obvious i am missing since i am new to kubernetes?
Thanks in advance.