aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-08-29 16:04:57 +0200
committerMorgan Richomme <morgan.richomme@orange.com>2020-01-21 15:45:59 +0000
commit4bd799e5dbcbf2131a685bf73319e962ace86f5c (patch)
tree7ee15b3061afed0633b8f79dcb467452aacd02d6
parent80a8b8c11d94af39ed26701dc10f2d3fc9e9a042 (diff)
Move Storage access to RWO
Today when deploying Robot with OOM, the PersistentVolumeClaim needs the "ReadWriteMany" (or "RWX") capability. According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes), ReadWriteMany stands for "the volume can be mounted as read-write by many nodes". That means that a particular PVC needs to be read and written from many pods. That also means that your code takes that into account and do the work to avoid write at the same place at the same time. An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon and Google storage classes). Robot PVC is used only for one Robot instance. Thus we don't need RWX. Issue-ID: INT-1230 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I300e34a9d4be40b36153812d2a99c458cae6b2c9
-rw-r--r--values.yaml2
1 files changed, 1 insertions, 1 deletions
diff --git a/values.yaml b/values.yaml
index c6ba420..544acdc 100644
--- a/values.yaml
+++ b/values.yaml
@@ -263,7 +263,7 @@ persistence:
## GKE, AWS & OpenStack)
##
# storageClass: "-"
- accessMode: ReadWriteMany
+ accessMode: ReadWriteOnce
size: 2Gi
mountPath: /dockerdata-nfs
mountSubPath: robot/logs