From 8a21103dcb1d7d9a135e80d7be27238b0e8e58b5 Mon Sep 17 00:00:00 2001 From: Andrey Zhavoronkov Date: Fri, 14 Aug 2026 11:16:23 +0300 Subject: [PATCH] docs: clarify RWX requirement for existing PVCs --- .../community/advanced/k8s_deployment_with_helm.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/site/content/en/docs/administration/community/advanced/k8s_deployment_with_helm.md b/site/content/en/docs/administration/community/advanced/k8s_deployment_with_helm.md index ce21016cea72..2d3287ebd662 100644 --- a/site/content/en/docs/administration/community/advanced/k8s_deployment_with_helm.md +++ b/site/content/en/docs/administration/community/advanced/k8s_deployment_with_helm.md @@ -376,6 +376,10 @@ kubectl delete deployments --namespace=foo -l app=cvat-app It is assumed that you have created a PersistentVolumeClaim named `my-claim-name` and a PersistentVolume that backing the claim. Claims must exist in the same namespace as the Pod using the claim. +The same claim can be mounted concurrently by several CVAT backend Pods. If these +Pods can be scheduled on different nodes, the backing volume must support the +`ReadWriteMany` (RWX) access mode. `ReadWriteOnce` (RWO) can be used only when all +Pods using the claim are scheduled on the same node. For details [see](https://kubernetes.io/docs/concepts/storage/persistent-volumes). Add these values in the `values.override.yaml`: ```yaml