Skip to content

fix: add OCP multus namespaceIsolation note #284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 16, 2025
Merged

fix: add OCP multus namespaceIsolation note #284

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/openshift/deployment-guide-openshift.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,6 +342,10 @@ In OCP, some components are deployed by default like Multus and CNI Plugins, whe

In addition, since there is no use of the Helm chart, the configuration should be done via the NicClusterPolicy CRD.

.. note::
In OCP, Multus is configured with `namespaceIsolation` enabled by default. This means that Pods using secondary networks should be deployed in the same namespace as the `network-attachment-definition` CR unless the NAD is in one of the following namespaces: `default`, `openshift-multus`, `openshift-sriov-network-operator` and `openshift-cnv`.
The namespace of the NAD can be set in the `networkNamespace` field in `HostDeviceNetwork`, `MacvlanNetwork`, `IPoIBNetwork`, `OVSNetwork` and `SriovNetwork`.

Following are examples of NicClusterPolicy configuration for OCP.

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Expand Down