Bug 1513764 - Allow egress router to run on non-default interface
Summary: Allow egress router to run on non-default interface
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.8.0
Assignee: Casey Callendrello
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks: 1513767 1513768
TreeView+ depends on / blocked
 
Reported: 2017-11-15 22:40 UTC by Dan Winship
Modified: 2020-01-31 19:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: The "assign-macvlan" pod annotation can now take the name of a network interface rather than just "true" or "false". Reason: Result: egress-routers can now be run on a non-default network interface
Clone Of:
: 1513767 1513768 (view as bug list)
Environment:
Last Closed: 2019-12-05 21:59:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dan Winship 2017-11-15 22:40:45 UTC 
Currently egress-routers always attach themselves to the network interface containing the default route. We need to make it possible to attach one to an alternate interface.

To get this out to a customer quickly, we're doing the simplest possible fix, which is to let the user manually specify a network interface (rather than, say, having OpenShift try to figure out the correct interface automatically based on EGRESS_SOURCE).
Comment 1 Dan Winship 2017-11-27 12:43:21 UTC 
https://github.com/openshift/origin/pull/17334
Comment 2 Ryan Howe 2017-12-07 18:56:22 UTC 
Just for reference:

The annotation will still accept true and false 

    pod.network.openshift.io/assign-macvlan: "true"

this allows it to accept further values like

    pod.network.openshift.io/assign-macvlan: "eth1"
Comment 8 Meng Bo 2018-03-07 10:44:38 UTC 
The bug has been fixed on v3.9.3
Note You need to log in before you can comment on or make changes to this bug.