I deployed a K3S Cluster on arm64 and I need to have a DFS directly on-premise, It will be better to have it running on the kubernetes stack. Regarding DFS choices there are some options, but...:

GlusterFS: Unfortunately CSI drivers is not currently supported on arm64.

CephFS: Unfortunately CSI drivers is not currently supported on arm64.

Longhorn: Only on armf.

OpenEBS: Dunno, did not test yet.

Rook(Ceph): CSI drivers not supported on arm64.

I tried to rebuild Docker image and binaries inside to be compatible on arm64 for Gluster and Ceph, but the point to failure seems to be the driver of course.

PS: in-tree drivers are being deprecated.

Do you have advices, solutions and documentations concerning my needs to have a DFS on k8s,k3s arm64 cluster?

Thank you have a good day.

  • Have you considered using NFS? I know NFS is not exactly a DFS solution but depending on what you want to achieve, it may be a good option. Check the answer on this case to check how to implement this solution. – Mark Watney Nov 27 '19 at 10:15
  • Our use case and environment does not allow us to have additional storage server for storage centralised (HA, backup....). So yes, I thought about this but for now I can not propose this solution. – GoA Oz Nov 28 '19 at 14:56
  • But you can use a pod for that purpose. – Mark Watney Nov 28 '19 at 15:08
  • You mean to have local storageclass? Yes, but I need to code all the sync between my nodes. Plus, I will not have the advantages of DFS with the option of storage block, recover, backup and hight availability... – GoA Oz Nov 28 '19 at 15:52

There’s work in progress to build OpenEBS’ JIVA storage engine on ARM64 arch: https://github.com/openebs/openebs/issues/1295

  • Thank you I will test it. – GoA Oz Dec 2 '19 at 7:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.