Hostpath across multiple nodes about csi-driver-host-path HOT 10 CLOSED

Btw, just to add info, the /storage/ folder directory is a shared directory that all nodes, both master and workers, can see this folder, so volumes created on top of that directory, is visible and accessible to all nodes

from csi-driver-host-path.

I am trying to use the hostpath csi across multiple nodes but am running into an issue

Why do you want to do that?

It is just an example driver that is used for testing. It is not designed to support running on multiple nodes. To make it reliable, topology support would have to be added.

from csi-driver-host-path.

We want to test it across nodes to test the storage layer underneath it, which is the presented globally across all nodes

I am not sure if we need a topology, because the same filesystem is presented across all nodes in the K8s cluster

Is there a way we can use it that way @pohly ?

from csi-driver-host-path.

Can't you use the builtin hostpath driver?

There are persistent local volumes (https://kubernetes.io/blog/2018/04/13/local-persistent-volumes-beta/) which you could configure to access your storage. Alternatively, an ephemeral hostpath volume (https://kubernetes.io/docs/concepts/storage/volumes/#hostpath) could also expose that path inside a pod for testing.

from csi-driver-host-path.

We could, but dont want to have the users having to include both the path and node names, but rather, have the CSI do it @pohly

from csi-driver-host-path.

I guess I still don't understand the goal. If it's just for testing (#49 (comment)), why are users involved (#49 (comment))?

from csi-driver-host-path.

Because we want to test all nodes creating and attaching the volumes on top of that global filesystem before we dedicate the time to create a full csi

Is it possible with this hostpath driver @pohly ? Again to test and enable users to see how it would work with that filesystem

from csi-driver-host-path.

No, I don't think this can be done with the hostpath driver. The driver assumes that the volume gets provisioned on the node where the volume is then also going to be used. It sounds like you want to provision once and then use on different nodes.

from csi-driver-host-path.

I was thinking of DaemonSets, can we use it in this case?

The volume and container can be provisioned in the same nodes still, what I want is for the driver to use all available nodes to provision the volume and container instead of only one node

I created a daemonset and was able to replicate the hostpath driver on all nodes, but for some reason, it fails when creating the volume and container on different nodes (again, they can be on the same node, I just want it to use all nodes to do that instead of only 1 node) @pohly

from csi-driver-host-path.

from csi-driver-host-path.