openebs VS local-path-provisioner

I run local-path-provisioner, openEBS (jiva) and minio on top of local-path storage.

volumeClaimTemplates: - metadata: name: mongo-persistent-storage spec: resources: requests: storage: 5G here in detail: https://github.com/openebs/openebs/blob/master/k8s/demo/mongodb/mongo-statefulset.yml

We are grateful for the support and contributions of the vibrant open-source community that OpenEBS has received. We are also thankful to the Cloud Native Computing Foundation (CNCF) for including OpenEBS as one of its storage projects. And a special thanks to the CNCF for being a reference user of OpenEBS as well - you can read about their experience and that of others including TikTok / ByteDance and Verizon / Yahoo on Adopters.md. Collectively, these aspects have helped my team to notice challenges and opportunities and of course to resolve bugs and improve the polish of OpenEBS with each release.

Deploy local-path-provisioner storage class but it does not support readwritemany so for high availability of your Kubernetes cluster better to use longhorn

I use this one. I'm waiting for the day it's combined with syncthing to sync across all nodes. https://github.com/rancher/local-path-provisioner

Just create 1 single partition and format it with whatevery filesystem you like. And then use ranchers local-path-provisioner which will create a folder per PV (k3s has this integrated by default).

It is better to use https://github.com/rancher/local-path-provisioner (or similar) for this case which will do PVC on local directories because manually linking PV<>PVC will not work.

Since you only have one physical node anyway, I would just make the cluster a single-node cluster (1 VM) and use local storage on that VM. I’m biased though because this is what I do (I run K3s and use local path provisioner).

With any of those tools, you'd implement a network storage on top of a network storage. I would go with mouting few volumes per node +local storage like (https://github.com/rancher/local-path-provisioner).

As I normally just Local-path from Rancher https://github.com/rancher/local-path-provisioner which is basically a wrapper around hostpath so from the application and container viewpoint it’s just a bind mount. Now I normally only use local-path for single node clusters and for distributed apps like database clusters which the application is making the data node redundant.

Rancher's local-path-provisioner (which uses hostPath or local under the hood)

I run local-path-provisioner, openEBS (jiva) and minio on top of local-path storage.