Bug 1124776

Summary:	Proxy Port documentation not sufficient
Product:	OpenShift Container Platform	Reporter:	Sebastian Faulhaber <sfaulhab>
Component:	Documentation	Assignee:	Bilhar <baulakh>
Status:	CLOSED EOL	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.2.0	CC:	jokerman, libra-onpremise-devel, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 20926, Cartridge Specification Guide-2-1.0 Build Date: 26-06-2014 11:39:45 Topic IDs: 20883-592387 [Latest]
Last Closed:	2016-06-28 00:35:14 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:
Embargoed:

Description Sebastian Faulhaber 2014-07-30 09:49:07 UTC

Title: Exposing Services

Describe the issue:
The explanation on how to expose public proxy ports is not described clearly in the current documentation. In addition to that the option "ssl_to_gear" is not contained.

Suggestions for improvement:
1) I would suggest to add chapter 4.2 from here as a general description of the concept: http://openshift.github.io/documentation/oo_system_architecture_guide.html#proxy-ports

2) In addition to that I would add an example based on the post on "ssl_to_gear" found here: https://www.openshift.com/content/at-least-one-port-for-external-use-excluding-8080-please#comment-31822

From my understanding this is the only way to get public proxy ports exposed with a non scalable gear at the moment. However please make sure that this is the way it's supposed to work from an OSE architecture point of view.

Additional information:

Comment 2 Bilhar 2016-06-28 00:35:14 UTC

Closing this BZ as there is no active development happening on 2.x docs, and only critical bugs are being addressed.

Please reopen if necessary.