aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/dmaap
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-09-02 14:18:42 +0200
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-09-02 14:18:42 +0200
commitcce22e94f92d81cf32328b32ca8af242516b8014 (patch)
tree875ac89dc191b4da132976ab881f4dd6da0c30dc /kubernetes/dmaap
parentcf745061a8c5bc2e0a9f9d99b2109295f3751198 (diff)
Move PORTAL Storage access to RWO
Today when deploying Portal 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). Portal PVC are only used by a mariadb instance or a cassandra instance. Thus we don't need RWX. Change-Id: I706e13759d3af829d61d7a33d068263aaf9e9158 Issue-ID: PORTAL-724 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'kubernetes/dmaap')
0 files changed, 0 insertions, 0 deletions