summaryrefslogtreecommitdiffstats
path: root/kubernetes/common
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-01-22 16:30:46 +0200
committerGerrit Code Review <gerrit@onap.org>2020-01-22 14:30:46 +0000
commit70fc0f2694d1353ea93437fc49415598f147d0ca (patch)
tree5e3cb8ae107f599008950ce8eea4cf89f9d712b9 /kubernetes/common
parent7dc067bbca304601b56559cec5df56a2631d018c (diff)
Update git submodules
* Update kubernetes/robot from branch 'master' to 4bd799e5dbcbf2131a685bf73319e962ace86f5c - 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
Diffstat (limited to 'kubernetes/common')
0 files changed, 0 insertions, 0 deletions