starlingx/docs
Code Issues Proposed changes

Update Bond Plugin WRCP docs

Browse Source 
Change-Id: I9deb5b3b912f8d9cd8987184f573f76437e05369
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2024-09-18 06:25:54 +00:00
parent 5686153306
commit 8f55a83caf
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/source/usertasks/kubernetes/integrate-the-bond-cni-plugin-2c2f14733b46.rst
View File

@ -71,7 +71,7 @@ see:
https://www.kernel.org/doc/Documentation/networking/bonding.txt
-----------------------------------------------------------------------------
Example: Launch a daemonset bonding two host interfaces in active-backup mode
Example: Launch a daemonset Bonding Two Host Interfaces in Active-backup mode
-----------------------------------------------------------------------------
The following example launches a daemonset bonding two host interfaces in
@ -155,8 +155,15 @@ the links list indicates the interfaces should be looked up on the host.
add:
- NET_ADMIN
.. note::
When a bond is configured in the container, interfaces are obtained from
the host network namespace and placed in a bonded interface in the
container network namespace. Therefore, it is not recommended to use
interfaces from the host that are assigned to the platform networks.
---------------------------------------------------------------------------
Example: Launch a pod with a bonded SR-IOV interface in 802.3ad (LACP) mode
Example: Launch a Pod With a Bonded SR-IOV Interface in 802.3ad (LACP) Mode
---------------------------------------------------------------------------
The following example launches a pod with a bonded |SRIOV| interface in
@ -165,7 +172,7 @@ defined links are made up of the ``net1`` and ``net2`` interfaces representing
the individual |SRIOV| interfaces.
The addition of ``"spoofchk": "off"`` in the ``pci_sriov_net_group0_data0``
``config`` block ensures that applications within the container have
``config`` block ensures that applications within the container have
permission to change the |MAC| address of the |VF|.
.. code-block:: yaml