Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
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).
You could also look into Longhorn, which is replicated storage.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
Related posts
- Diskomator – NVMe-TCP at your fingertips
- Difference between snapshot-cleanup and snapshot-delete in Longhorn recurring job?
- Ask HN: Any of you run Kubernetes clusters in-house?
- Container redundancy with multiple Unraid servers?
- How do I clean up a Longhorn volume? Trimming the volume doesn't work, "cannot find a valid mountpoint for volume"