Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1419184 - Is F5 integration documentation is correct for 3.4?
Summary: Is F5 integration documentation is correct for 3.4?
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-03 20:25 UTC by Shanna Chan
Modified: 2019-08-10 06:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-10 06:46:21 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Shanna Chan 2017-02-03 20:25:24 UTC
Document URL: 
It is not clear that in the OCP 3.4 documentation for F5 integration for OCP.
#1) https://docs.openshift.com/container-platform/3.4/install_config/router/f5_router.html

Per my understand from BU:
Feature(s):  F5 Routing Enhancements 

Description: An on-ramp node is no longer needed to bridge the F5 to OpenShift. The F5 gets an SDN IP from the cluster CIDR, so OpenShift can communicate directly with the F5 with current information about nodes, hostsubnets, services, routes, endpoints, and VNIDs.


Section Number and Name: 
https://docs.openshift.com/container-platform/3.4/install_config/router/f5_router.html#deploying-the-f5-router

To deploy the F5 router:

Step #1. First, establish a tunnel using a ramp node, which allows for the routing of traffic to pods through the OpenShift Container Platform SDN.

Is step #1 referring to https://docs.openshift.com/container-platform/3.4/install_config/routing_from_edge_lb.html#install-config-routing-from-edge-lb setup? if so, please specific.

Describe the issue: 
Why do we still need ramp node in Step #1?
If not, what exact step we need to do to set thing up?


Suggestions for improvement: 
Again in OCP 3.4, my understanding was that ramp node is not required which does not match the documentation. 
Please update the documentation accordingly if the F5 integration has changed.



Additional information:


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