Rook Agent Pods fail to start about kube-linode HOT 2 CLOSED

Same here. In fact yesterday I tried to spin up a cluster of three nodes and it failed to start rook pod.

At first it failed with RBAC error, which I fixed by adding rook-operator serviceaccount to cluster-admin clusterrole.

After that it failed with error saying that it couldn't detect pod name, which was fixed by adding env var POD_NAME to the rook-operator container.

And then I ran into issue described above where apparently it was trying to write to read only mounted volume.

I tried to add volume-plugin argument as KUBELET-ARGS environment variables, tried to add it directly to kubelet-wrapper in kubelet service, but unfortunately with no luck.

Any suggestions welcome.

from kube-linode.

Should be fixed now with #53. cc @displague.

from kube-linode.