Abhinandan Purkait

Hi, we have made a fix for this and the change is currently on develop. So for managed services where hostname differs from node name, we can remove these flags...

@Winter-Guerra Yes, rightly pointed out, the fix has been made, now we register using the nodename, the `csi-driver` code has now been moved to [mayastor-control-plane](https://github.com/openebs/mayastor-control-plane/tree/develop/control-plane/csi-driver). You can check the code...

> Still facing the problem following the official deployment guide: https://mayastor.gitbook.io/introduction/quickstart/deploy-mayastor > > Any progress on it? It's really frustrated for people willing to try mayastor. Hi, we are to...

Hi, we have made a fix for this and the change is currently on [release/1.0.2](https://github.com/openebs/mayastor/tree/release/1.0.2). Can you please try with it?. You can use the [`mayastor-daemonset`](https://github.com/openebs/mayastor/blob/release/1.0.2/deploy/mayastor-daemonset.yaml) yaml from the deploy...

bors try

Hi, @Daxcor69 can we take a look at the logs of `csi-node` pods on the `storage1` node? Seems like the `csi-node` pod has not come up successfully on that node.

Can we see the csinode object on storage1, i.e `kubectl get csinode storage1 -oyaml`?

Seems like the mayastor csi driver is not registered! Can you restart the csi-node pod on storage1 and check if that changes anything in the csinode object?

Can you share the storageclass yaml that you have used here?

@AichaDevOps The helper pod need to be launched in privileged mode. This is because on nodes, pods without privileged access cannot write to the host directory. Helper pods need to...