From 9a37e948ce2db17f37bde037f449650afc89857f Mon Sep 17 00:00:00 2001 From: David Kowalski <50632861+david-kow@users.noreply.github.com> Date: Mon, 27 Jan 2020 15:04:08 +0100 Subject: [PATCH] Add note about Kibana accessing ESs in other namespaces (#2466) (#2471) * Add note about Kibana accessing ESs in other namespaces * Update docs/kibana.asciidoc Co-Authored-By: Peter Brachwitz Co-authored-by: Peter Brachwitz Co-authored-by: Peter Brachwitz --- docs/kibana.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/kibana.asciidoc b/docs/kibana.asciidoc index 2e5a4647fa..59bb2f30f4 100644 --- a/docs/kibana.asciidoc +++ b/docs/kibana.asciidoc @@ -38,6 +38,8 @@ spec: NOTE: `namespace` is optional if the Elasticsearch cluster is running in the same namespace as Kibana. +NOTE: Any Kibana can reference (and thus access) any Elasticsearch instance as long as they both are in namespaces that are watched by the same ECK instance. ECK will copy the required `Secret` from Elasticsearch to Kibana namespace. If this behavior is not desired, more than one ECK instance can be deployed. Kibana won't be able to automatically connect to Elasticsearch (through `elasticsearchRef`) in a namespace managed by a different ECK instance. + The Kibana configuration file is automatically setup by ECK to establish a secure connection to Elasticsearch. [float]