-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.14, 4.15, 4.16, 4.17, 4.18, 4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
8
-
None
-
None
-
-
None
-
None
-
None
-
T&PS 2025 #6, T&PS 2025 #7, T&PS 2025 #8
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When planning https://issues.redhat.com/browse/TELCODOCS-2278 it became apparent that documentation does not exist for an important supported secondary network of bond cni.
No mention here:
- https://docs.okd.io/4.18/networking/multiple_networks/understanding-multiple-networks.html#additional-networks-provided_understanding-multiple-networks
- https://docs.okd.io/4.18/networking/multiple_networks/understanding-multiple-networks.html#additional-networks-provided_understanding-multiple-networks
No example here: https://docs.okd.io/4.18/networking/multiple_networks/secondary_networks/creating-secondary-nwt-other-cni.html
SR-IOV config https://docs.okd.io/4.18/networking/hardware_networks/using-pod-level-bonding.html#nw-sriov-cfg-creating-bond-network-attachment-definition_using-pod-level-bonding above may be enough to cover worked example of bond CNI with SR-IOV.
See here around since 4.10 https://www.redhat.com/en/blog/bonds-in-openshift-pods
This would be good to replicate in the docs as per standard we follow for other CNIs. We do cover wrt to SR-IOV but no specific standalone mention. See https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/networking/hardware-networks#nw-sriov-cfg-bond-interface-with-virtual-functions_using-pod-level-bonding
NOTE: OCP only supports bond CNI with SR-IOV VFs (as detailed in the docs)
Additional references
https://github.com/k8snetworkplumbingwg/bond-cni
https://www.redhat.com/en/blog/using-the-multus-cni-in-openshift
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: