From cff39362d8942e784bfae2dc0f2cda05beccc091 Mon Sep 17 00:00:00 2001 From: Priyanka Date: Thu, 17 May 2018 04:05:22 +0000 Subject: [PATCH] nsPrefix Changes for Log Issue-ID: OOM-1028 Change-Id: I1923cbbf75bdf7eead3da506a1c2bb3766f83d31 Signed-off-by: Priyanka --- .../log/charts/log-elasticsearch/resources/config/elasticsearch.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/kubernetes/log/charts/log-elasticsearch/resources/config/elasticsearch.yml b/kubernetes/log/charts/log-elasticsearch/resources/config/elasticsearch.yml index abdab8beb5..8bbb01997e 100644 --- a/kubernetes/log/charts/log-elasticsearch/resources/config/elasticsearch.yml +++ b/kubernetes/log/charts/log-elasticsearch/resources/config/elasticsearch.yml @@ -86,7 +86,6 @@ network.host: 0.0.0.0 # By default, Elasticsearch will bind to the available loopback addresses and will scan ports 9300 to 9305 to try # to connect to other nodes running on the same server. # -#discovery.zen.ping.unicast.hosts: ["elasticsearch.{{.Values.nsPrefix}}" #$discovery.zen.ping.unicast.hosts # # This setting tells Elasticsearch to not elect a master unless there are enough master-eligible nodes -- 2.16.6