Mayastor VS ansible-role-k3s

What I really want is a filesystem I can span across geographically remote nodes that's transparently compatible. I should just be able to chuck files into it from my NAS like any other. I think Mayastor [1] might get some of the way there?

[1] https://github.com/openebs/mayastor

Since you're using NVMe's there is some Intel tech that has people making some outrageous claims about mayastor. It's primarily used in OpenEBS for Kubernetes clusters, but from what I've seen, it looks possible to strip it down to the bare essentials to serve blocks.

I use Longhorn for my set up, you can checkout the config here. But Mayastor just released v1.0 so I'll try that.

Advances in OpenEBS 3.0 in the vertical dimension, including addition resilience with performance via Mayastor, (beta) include:

Tried OpenEBS? These two have replication HA features. https://github.com/openebs/Mayastor https://github.com/openebs/cstor-operators

There is another very good ansible role for k3s, actually better than mine

if you have experience with ansible you can use https://github.com/PyratLabs/ansible-role-k3s

Not OP but there's an excellent galaxy ansible role for k3s and it's idempotent, so if you want to upgrade to a newer version of k3s or tweak settings, or add a node it's supported.

Take it to the next level and let git be the source of truth for k8s using Flux! My home cluster repo is exactly that plus I'm using the ansible-k3s-role Galaxy role. It's based on this k8s at home template.

If you are comfortable with ansible there's a nice Galaxy role that I use.

Experience has been good so far but this is the first I saw of KubeEdge. I’m going to give it an evaluation. I used Ansible https://github.com/PyratLabs/ansible-role-k3s to set up the cluster with some minor adaptions and cleanup scripts.