1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00

TELCODOCS-2274-RN Adding RN for namespaced SR-IOV

This commit is contained in:
Kevin Quinn
2025-09-16 13:16:15 +01:00
parent b785070b99
commit fbd3187dc1

View File

@@ -550,6 +550,21 @@ In this release you can now specify the transmit hash policy for load balancing
For more information, see xref:../networking/multiple_networks/secondary_networks/creating-secondary-nwt-other-cni.adoc#nw-multus-bond-cni-object_configuring-additional-network-cni[Configuration for a Bond CNI secondary network].
[id="ocp-4-20-networking-namespaced-sriov-app-owners_{context}"]
==== SR-IOV network management in application namespaces
With {product-title} {product-version}, you can now create and manage SR-IOV networks directly within your application namespaces. This new feature provides greater control over your network configurations and helps simplify your workflow.
Previously, creating an SR-IOV network required a cluster administrator to configure it for you. Now, you can manage these resources directly in your own namespace, which offers several key benefits:
* Increased autonomy and control: You can now create your own `SriovNetwork` objects, removing the need to involve a cluster administrator for network configuration tasks.
* Enhanced security: Managing resources within your own namespace improves security by providing better separation between applications and helps prevent unintentional misconfigurations.
* Simplified permissions: You can now simplify permissions and reduce operational overhead by using namespaced SR-IOV networks.
For more information, see xref:../networking/hardware_networks/configuring-namespaced-sriov-resources.html#configuring-namespaced-sriov-resources[Configuring namespaced SR-IOV resources].
[id="ocp-release-notes-nodes_{context}"]
=== Nodes