Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513764 - Allow egress router to run on non-default interface [NEEDINFO]
Summary: Allow egress router to run on non-default interface
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.8.0
Assignee: Dan Winship
QA Contact: Meng Bo
Depends On:
Blocks: 1513767 1513768
TreeView+ depends on / blocked
Reported: 2017-11-15 22:40 UTC by Dan Winship
Modified: 2018-03-28 09:35 UTC (History)
7 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)
Last Closed:
Target Upstream Version:
danw: needinfo? (smunilla)

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

Comment 2 Ryan Howe 2017-12-07 18:56:22 UTC
Just for reference:

The annotation will still accept true and false "true"

this allows it to accept further values like "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.