From 9b699d7e181874f9fa485d9b7dceece9f12b3b36 Mon Sep 17 00:00:00 2001 From: Badre Tejado Date: Tue, 21 Oct 2025 14:25:37 +0000 Subject: [PATCH 1/2] Clarify NFS limitations, quota, and solutions (CRW-9475) --- .../pages/configuring-storage.adoc | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/modules/administration-guide/pages/configuring-storage.adoc b/modules/administration-guide/pages/configuring-storage.adoc index 7d6014a460..3e54c23a57 100644 --- a/modules/administration-guide/pages/configuring-storage.adoc +++ b/modules/administration-guide/pages/configuring-storage.adoc @@ -7,9 +7,19 @@ [id="configuring-storage"] = Configuring storage -[WARNING] +[IMPORTANT] + +.Understanding supported storage protocols and requirements + ==== -{prod-short} does not support the Network File System (NFS) protocol. +OpenShift Dev Spaces workspaces require storage with **volumeMode: FileSystem** because the development environment is designed to store project files, code, and configurations in a standard, hierarchical directory structure (such as /projects). + +While Network File System (NFS) is one of the few protocols that natively supports the necessary **ReadWriteMany (RWX)** access mode for running concurrent workspaces (the Per-User strategy), standard {Kubernetes} NFS provisioning presents certain operational challenges: + +* *Quota Enforcement Failure:* Kubernetes Persistent Volume Claims (PVCs) cannot reliably enforce storage quotas on a generic NFS volume. This limitation means a single workspace could exceed its allocated storage, potentially consuming the entire shared volume and leading to resource exhaustion, which causes widespread instability for all other users. +* *Stability and Concurrency:* Generic NFS implementations often lack the robust locking and cache coherency required to maintain data integrity when multiple cluster nodes access the same volume concurrently, potentially leading to workspace instability. + +To overcome these stability and quota issues, it is recommended to use certified **clustered or managed storage solutions** that provide robust CSI drivers. These solutions use the NFS protocol but enforce enterprise-grade features, including strict quota enforcement and high-performance RWX file access, ensuring reliable operation for the Per-User strategy. Examples include community-supported distributed storage projects or third-party CSI drivers offered by most cloud providers. ==== * xref:configuring-storage-classes.adoc[] From 043e1410217c2110bff1d14e7d6da18fabd785b9 Mon Sep 17 00:00:00 2001 From: Badre Tejado-Imam Date: Mon, 3 Nov 2025 09:36:28 -0500 Subject: [PATCH 2/2] Update modules/administration-guide/pages/configuring-storage.adoc Co-authored-by: David Kwon --- modules/administration-guide/pages/configuring-storage.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/administration-guide/pages/configuring-storage.adoc b/modules/administration-guide/pages/configuring-storage.adoc index 3e54c23a57..7fcfdc3952 100644 --- a/modules/administration-guide/pages/configuring-storage.adoc +++ b/modules/administration-guide/pages/configuring-storage.adoc @@ -12,7 +12,7 @@ .Understanding supported storage protocols and requirements ==== -OpenShift Dev Spaces workspaces require storage with **volumeMode: FileSystem** because the development environment is designed to store project files, code, and configurations in a standard, hierarchical directory structure (such as /projects). +{prod} workspaces require storage with **volumeMode: FileSystem** because the development environment is designed to store project files, code, and configurations in a standard, hierarchical directory structure (such as /projects). While Network File System (NFS) is one of the few protocols that natively supports the necessary **ReadWriteMany (RWX)** access mode for running concurrent workspaces (the Per-User strategy), standard {Kubernetes} NFS provisioning presents certain operational challenges: