Our great sponsors
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- InfluxDB - Access the most powerful time series database as a service
- SonarLint - Clean code begins in your IDE with SonarLint
- CodiumAI - TestGPT | Generating meaningful tests for busy devs
-
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.
-
ONLYOFFICE
ONLYOFFICE Docs — document collaboration in your environment. Powerful document editing and collaboration in your app or environment. Ultimate security, API and 30+ ready connectors, SaaS or on-premises
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
- How do I clean up a Longhorn volume? Trimming the volume doesn't work, "cannot find a valid mountpoint for volume"
- Is there a tool to manage the resources of individual containers in an easy, visual way? Currently containers devour every VM resource, when I set 20GB RAM, they will consume 20GB. I want to set limits for each container, doing it in docker compose is inconvenient.
- Quiet Cluster for Microservice Software Dev
- Low power ceph setup?
- EKS Storage with autoscale