Bug 1368263

Summary:	Structural issues with F5 integration in containerized Openshift
Product:	OpenShift Container Platform	Reporter:	Steven Walter <stwalter>
Component:	Networking	Assignee:	Rajat Chopra <rchopra>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	aos-bugs, bbennett, cstephen, eparis, erich, misalunk, ramr, rchopra
Version:	3.2.0
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:	2016-10-28 16:47:26 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 Steven Walter 2016-08-18 21:07:57 UTC

From the customer:

- integrating openshift enterprise 3.2.0 with F5 LTM infrastructure 
- deploying to a containerized environment, in that openshift-master-* , openshift-node and openvswitch are all in docker containers themselves. Using the setup guide for ramp nodes at https://docs.openshift.com/enterprise/3.2/install_config/install/deploy_router.html
- Number of issues (see priv comment for details)

Comment 6 Rajat Chopra 2016-09-02 20:18:09 UTC

Sorry, there are no workarounds (we can make some), but the actual feature will land faster than the workarounds. By actual feature I mean these two cards:
1. https://trello.com/c/fnW1tPCY/155-8-f5-integration-get-lease-from-cluster-cidr
2. https://trello.com/c/ReyAHKTb/157-8-get-the-router-pod-to-program-the-f5

The basic idea is to get rid of the ramp node entirely and let the F5 appliance encode the VxLAN traffic into the SDN by itself.

Comment 7 Steven Walter 2016-09-06 18:08:00 UTC

So then we are looking at 3.4 as the earliest, if potential workarounds are not feasible to get done?

Comment 18 Ben Bennett 2016-10-28 16:47:26 UTC

Closing because there is an article on how to configure things so they persist:
  https://access.redhat.com/articles/2677771