elastic: update masterService in manifest
For dual controller configs with no workers, the elasticsearch-data pods will be configured as master-capable. This means the corresponding service should be listed in the discovery.seed_hosts along with the master service. Use the template's masterService setting to configure this. For configs with 3 master pods and the data pods are not master- capable this setting will not hurt. Without this setting, if the sole master pod went down for any reason including manual delete or application-update, it would not be able to rejoin the cluster. Change-Id: I19302956bf079850459125ea4dd73a0d9c4365cb Story: 2005733 Task: 37259 Signed-off-by: Kevin Smith <kevin.smith@windriver.com>
This commit is contained in:
parent
c6821614fb
commit
6716be451f
@ -101,6 +101,7 @@ data:
|
||||
image: docker.elastic.co/elasticsearch/elasticsearch-oss
|
||||
imageTag: 7.4.0
|
||||
esMajorVersion: 7
|
||||
masterService: 'mon-elasticsearch-data-headless, mon-elasticsearch-master'
|
||||
wait:
|
||||
labels:
|
||||
release: mon-elasticsearch-data
|
||||
@ -169,6 +170,7 @@ data:
|
||||
image: docker.elastic.co/elasticsearch/elasticsearch-oss
|
||||
imageTag: 7.4.0
|
||||
esMajorVersion: 7
|
||||
masterService: 'mon-elasticsearch-data-headless, mon-elasticsearch-master'
|
||||
wait:
|
||||
labels:
|
||||
release: mon-elasticsearch-client
|
||||
@ -217,6 +219,7 @@ data:
|
||||
image: docker.elastic.co/elasticsearch/elasticsearch-oss
|
||||
imageTag: 7.4.0
|
||||
esMajorVersion: 7
|
||||
masterService: 'mon-elasticsearch-data-headless, mon-elasticsearch-master'
|
||||
wait:
|
||||
labels:
|
||||
release: mon-elasticsearch-master
|
||||
@ -253,7 +256,7 @@ data:
|
||||
type: pod
|
||||
values:
|
||||
image:
|
||||
repository: untergeek/curator
|
||||
repository: docker.io/untergeek/curator
|
||||
tag: 5.7.6
|
||||
env:
|
||||
FILEBEAT_INDEX_LIMIT_GB: 48
|
||||
|
Loading…
x
Reference in New Issue
Block a user