Bug 1827375

Summary: Multus namespaceIsolation should allow references to CRD in the default namespace
Product: OpenShift Container Platform Reporter: Douglas Smith <dosmith>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: aconstan, bbennett
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: SDN-CI-IMPACT,SDN-BP
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1827377 (view as bug list) Environment:
Last Closed: 2020-05-26 16:50:32 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:
Bug Depends On: 1827377    
Bug Blocks:    

Description Douglas Smith 2020-04-23 18:52:51 UTC 
Multus CNI when using namespaceIsolation prevents pods from accessing NetworkAttachmentDefinitions outside of the namespace of a pod where that net-attach-def is referenced (via annotation). 

The proposed fix to to allow pods to reference the default namespace from any given namespace. Therefore, if you had a configuration named "macvlan-conf" and had stored it in the default namespace, you could reference it from an annotation (from either within or outside of the default namespace) as "default/macvlan-conf".

The current provides to be painful for users at time. One current such case is that when integrating with Istio (in a non-chained-cni-plugin-mode) users must create NetworkAttachmentDefinition in every namespace which uses Istio.

This may also prove useful in other scenarios where you have commonly used net-attach-def that may be inconvenient to create in a number of different namespaces.
Comment 3 Weibin Liang 2020-05-18 14:52:46 UTC 
Tested and verified in 4.4.0-0.nightly-2020-05-18-115348
Comment 5 errata-xmlrpc 2020-05-26 16:50:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2180