Bug 1280411 - [docs] list ports required for openshift environment connectivity
Summary: [docs] list ports required for openshift environment connectivity
Keywords:
Status: CLOSED DUPLICATE of bug 1270960
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL: https://access.redhat.com/documentati...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-11 16:57 UTC by Evgheni Dereveanchin
Modified: 2015-11-11 20:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-11 20:26:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1520653 0 None None None Never
Red Hat Knowledge Base (Solution) 1751123 0 None None None Never

Description Evgheni Dereveanchin 2015-11-11 16:57:26 UTC 
Document URL: 
https://access.redhat.com/documentation/en/openshift-enterprise/version-3.0/openshift-enterprise-30-installation-and-configuration/chapter-2-installing#prereq-networking
Section Number and Name: 
2.2.3. Environment Requirements -> Networking
Describe the issue: 
OpenShift Enterprise can be installed in a Cloud environment (RHOSE/AWS/Azure/etc) where security groups need to be defined to allow node communication. Currently it is not mentioned that certain ports need to be open for the environment to operate, for example UDP/4789 essential for SDN operation.
Suggestions for improvement: 
Document required ports and functions
Additional information: 
this is currently covered in Knowledge Base articles:
https://access.redhat.com/solutions/1520653
https://access.redhat.com/solutions/1751123
Comment 1 Vikram Goyal 2015-11-11 20:26:54 UTC 

*** This bug has been marked as a duplicate of bug 1270960 ***
Note You need to log in before you can comment on or make changes to this bug.