The current implementation of configuring the Elasticsearch proxy url in Kibana is too rigid. I shouldn't be required to define a port number.
This issue was identified when attempting to use this image in Kubernetes, which hides the service port assignment. I should be able to define my url and produce the following result:
The current implementation of configuring the Elasticsearch proxy url in Kibana is too rigid. I shouldn't be required to define a port number.
This issue was identified when attempting to use this image in Kubernetes, which hides the service port assignment. I should be able to define my url and produce the following result:
https://<my_ip>/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging/_nodes
As it stands now, the port number is included in the URL:
https://<my_ip>/api/v1beta3/proxy/namespaces/default/services/elasticsearch-logging:9200/_nodes