Hide Forgot
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)
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.
So then we are looking at 3.4 as the earliest, if potential workarounds are not feasible to get done?
Closing because there is an article on how to configure things so they persist: https://access.redhat.com/articles/2677771