Bug 1512126

Summary:	[RFE] Ability to set which IFACE will be used for macvlan of egress router.
Product:	OpenShift Container Platform	Reporter:	Ryan Howe <rhowe>
Component:	RFE	Assignee:	Eric Paris <eparis>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	aos-bugs, erich, jokerman, mmccomas
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:	2019-06-12 11:56:58 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:
Embargoed:

Description Ryan Howe 2017-11-10 22:32:15 UTC

Description of problem:

At this time mavlan for the egress router is only attached to the default iface. 

https://github.com/openshift/origin/blob/release-3.6/pkg/sdn/plugin/pod_linux.go#L85
https://github.com/openshift/origin/blob/release-3.7/pkg/network/node/pod.go#L379


This RFE is to request the ability to define which iface will be used for the macvlan to attach too when the egress router is scheduled to a node.

Comment 2 Marcos Garcia 2017-11-17 14:29:52 UTC

Customer's version



OpenShift Master:

v3.6.173.0.21

Kubernetes Master:

v1.6.1+5115d708d7

Comment 3 Marcos Garcia 2017-11-17 14:35:31 UTC

As a reminder, Dan Winship suggested re-using the existing decorator

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

and accept further values like

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

or in our case, which will be a bonded vlan device (bond1.558)

For more info on the egress router pod macvlan feature, see https://docs.openshift.com/container-platform/3.6/admin_guide/managing_pods.html#admin-guide-deploying-an-egress-router-pod

Comment 5 Kirsten Newcomer 2019-06-12 11:56:58 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.