Bug 1670161

Summary:	[DOCS] Add documentation on "getting traffic into a cluster" for the dedicated customers
Product:	OpenShift Online	Reporter:	Eric Jones <erjones>
Component:	Documentation	Assignee:	Andrew Taylor <antaylor>
Status:	CLOSED NOTABUG	QA Contact:	Eric Jones <erjones>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	3.x	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.x
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:	2020-01-10 20:28:49 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 Eric Jones 2019-01-28 19:12:50 UTC

Document URL: 
N/A

Describe the issue: 
Dedicated users do not have any official information on getting traffic into their cluster. We have existing documentation for standard OCP [0] that likely could be used to create a similar doc for dedicated.

[0] https://docs.openshift.com/container-platform/3.9/dev_guide/expose_service/expose_internal_ip_load_balancer.html#getting-traffic-into-cluster-load

Comment 2 Andrew Taylor 2020-01-10 20:28:49 UTC

This bug is related to 3.9, which is no longer supported. I will archive this bug at this time. 

As for related documentation in 3.11, we have sections on exposing TCP routes: 
https://docs.openshift.com/dedicated/3/getting_started/access_your_services.html

How to create routes: 
https://docs.openshift.com/dedicated/3/dev_guide/routes.html

And a section on route types: 
https://docs.openshift.com/dedicated/3/architecture/networking/routes.html

As this topic is sufficiently covered in supported documentation, I will archive this bug at this time. 

Please let me know if you have any questions or concerns.