nextcloud/all-in-one

[HELM] Add support for RWO Volumes in Single-Node Setups

Closed this issue · 0 comments

MSandro commented

Feature Request: Add support for RWO Volumes in Single-Node Setups

Is your feature request related to a problem? Please describe.

Nextcloud AIO currently enforces the use of a ReadWriteMany (RWX) volume for the main Nextcloud storage.
In single-node Kubernetes setups, this requirement is unnecessary and often not feasible, as many storage backends (like local persistent volumes or simple block storage) only support ReadWriteOnce (RWO).

This limitation makes it difficult or even impossible to run Nextcloud AIO in small or home-lab clusters where RWX storage is not available.

Describe the solution you'd like

Introduce a Helm Chart parameter (e.g. nextcloud.volumeAccessMode) that allows choosing between ReadWriteMany (default) and ReadWriteOnce.

This way:

  • Multi-node setups can continue using RWX as required.
  • Single-node setups can override the default and use RWO storage.

Describe alternatives you've considered

  • Patching the Helm Chart locally to switch accessModes from RWX to RWO. This is fragile and makes upgrades harder.
  • Using NFS or another RWX provider even in single-node clusters, which introduces unnecessary complexity and overhead.
  • Using hostPath volumes, which is discouraged and not ideal for production.

Additional context

Allowing an optional RWO setting would make Nextcloud AIO more accessible for home-lab and single-node users, without impacting multi-node deployments where RWX is required.