Can you explain what exactly you mean by routing awareness in case of Kibana? As Kibana is mostly translating/forwarding Elasticsearch requests, it will benefit from this ES setting as well, as the requests issued by Kibana will respect these settings as well.
One related thing I can think of - it's a common pattern to have a coordinating Elasticsearch node running along with the Kibana instance on the same host and have Kibana only connected to this node. This way the full power of Elasticsearch routing logic can be leveraged.
Ah, I see, thanks a lot for this explanation. To my knowledge Kibana doesn't offer any features around this. In this case the "routing awareness" would be setting elasticsearch.hosts to just the ES hosts in the same zone or a single dedicated coordinating node just for Kibana in that zone - Kubernetes would have to handle this additional complexity.
I have almost no Kubernetes knowledge (as you probably realized by now), but "topology aware hints" seem like a related feature: Topology Aware Hints | Kubernetes
Maybe you could also create a single pod which contains Kibana and Elasticsearch coordinating node together.
"Topology Aware Hints" feature is very new and our cluster is not able to do it now but great idea !
One pod with ES+Kibana could be a good solution too.
I will try these solutions, thank you very much !!!
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.