Bug 1403952

Summary: [RFE] Expose Elasticsearch as a route
Product: OpenShift Container Platform Reporter: Erez Freiberger <efreiber>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED CURRENTRELEASE QA Contact: Johnny Liu <jialiu>
Severity: low Docs Contact:
Priority: medium    
Version: 3.4.0CC: aos-bugs, bleanhar, efreiber, jokerman, mmccomas, rmeggins
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-24 18:16:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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
Comment 5 Rich Megginson 2017-08-24 18:13:23 UTC 
Fixed in 3.6: https://github.com/openshift/openshift-ansible/blob/release-3.6/roles/openshift_logging_elasticsearch/tasks/main.yaml#L329