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.
Customer's version OpenShift Master: v3.6.173.0.21 Kubernetes Master: v1.6.1+5115d708d7
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
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.