summaryrefslogtreecommitdiffstats
path: root/kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-09-02 15:03:59 +0200
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-09-02 15:03:59 +0200
commit3bcc510b3ecfa7d169edf101764a0c1c843090ca (patch)
tree49e4c70e1385c3d7170b85f502ad551b2aadeb14 /kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml
parentcf745061a8c5bc2e0a9f9d99b2109295f3751198 (diff)
Move Modeling Storage to RWO
Today when deploying Policy 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). Modeling PVC for is used only for one POD. Thus we don't need RWX. Change-Id: Ic4b8f5a336f2b9edfdf25ef3cc549b389f9b6f65 Issue-ID: MODELING-213 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml')
0 files changed, 0 insertions, 0 deletions