Merge pull request #32540 from aireilly/BZ1938270

updates for BZ1938270

Author: ahardin-rh

modules/cnf-assigning-a-secondary-network-to-a-vrf.adoc

@@ -8,6 +8,11 @@
 
 As a cluster administrator, you can configure an additional network for your VRF domain by using the CNI VRF plug-in. The virtual network created by this plug-in is associated with a physical interface that you specify.
 
+[NOTE]
+====
+Applications that use VRFs need to bind to a specific device. The common usage is to use the `SO_BINDTODEVICE` option for a socket. `SO_BINDTODEVICE` binds the socket to a device that is specified in the passed interface name, for example, `eth1`. To use `SO_BINDTODEVICE`, the application must have `CAP_NET_RAW` capabilities.
+====
+
 [id="cnf-creating-an-additional-network-attachment-with-the-cni-vrf-plug-in_{context}"]
 == Creating an additional network attachment with the CNI VRF plug-in
 

modules/cnf-assigning-a-sriov-network-to-a-vrf.adoc

@@ -9,6 +9,11 @@ As a cluster administrator, you can assign an SR-IOV network interface to your V
 
 To do this, add the VRF configuration to the optional `metaPlugins` parameter of the `SriovNetwork` resource.
 
+[NOTE]
+====
+Applications that use VRFs need to bind to a specific device. The common usage is to use the `SO_BINDTODEVICE` option for a socket. `SO_BINDTODEVICE` binds the socket to a device that is specified in the passed interface name, for example, `eth1`. To use `SO_BINDTODEVICE`, the application must have `CAP_NET_RAW` capabilities.
+====
+
 [id="cnf-creating-an-additional-sriov-network-with-vrf-plug-in_{context}"]
 == Creating an additional SR-IOV network attachment with the CNI VRF plug-in