From 966f2e4efd83c2c037427b7ab617442793236354 Mon Sep 17 00:00:00 2001 From: Andrey Zhavoronkov Date: Fri, 2 Dec 2022 17:57:04 +0200 Subject: [PATCH] Added note about use of existing PVs to store CVAT data (#5413) --- .../advanced/k8s_deployment_with_helm.md | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/site/content/en/docs/administration/advanced/k8s_deployment_with_helm.md b/site/content/en/docs/administration/advanced/k8s_deployment_with_helm.md index 9791c382..e0955b59 100644 --- a/site/content/en/docs/administration/advanced/k8s_deployment_with_helm.md +++ b/site/content/en/docs/administration/advanced/k8s_deployment_with_helm.md @@ -248,3 +248,39 @@ To fix that, delete CVAT Deployments before upgrading ```shell kubectl delete deployments --namespace=foo -l app=cvat-app ``` +### How to use existing PersistentVolume to store CVAT data instead of default storage +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. +For details [see](https://kubernetes.io/docs/concepts/storage/persistent-volumes). +Add these values in the `values.override.yaml`: +```yaml +cvat: + backend: + permissionFix: + enabled: false + defaultStorage: + enabled: false + server: + additionalVolumes: + - name: cvat-backend-data + persistentVolumeClaim: + claimName: my-claim-name + worker: + default: + additionalVolumes: + - name: cvat-backend-data + persistentVolumeClaim: + claimName: my-claim-name + low: + additionalVolumes: + - name: cvat-backend-data + persistentVolumeClaim: + claimName: my-claim-name + utils: + additionalVolumes: + - name: cvat-backend-data + persistentVolumeClaim: + claimName: my-claim-name + +```