Bug 1403952 - [RFE] Expose Elasticsearch as a route
Summary: [RFE] Expose Elasticsearch as a route
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 17:13 UTC by Erez Freiberger
Modified: 2017-08-24 18:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-24 18:16:38 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Erez Freiberger 2016-12-12 17:13:17 UTC
Description of problem:
Currently an Elasticsearch installed with hosted logging is not accessible beside through Kibana. 
A route to the Elasticsearch service is needed (Both to the normal one and to the ops logging one). Ideally those routes names can should be configurable from the inventory file in the same manner that the Kibana routes are configured.


Version-Release number of selected component (if applicable): 3.4.z


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
A route to the Elasticsearch service is needed (Both to the normal one and to the ops logging one).


Additional info:


[1]http://richmegginson.livejournal.com/28981.html


Note You need to log in before you can comment on or make changes to this bug.