Merge pull request #96525 from kquinn1204/TELCODOCS-2278

Add transmit hash policy to bond CNI (Tech Preview)

Author: amolnar-rh

modules/nw-multus-bond-cni-object.adoc

@@ -44,6 +44,10 @@ The following table describes the configuration parameters for the Bond CNI plug
 |`string`
 |Specifies the bonding policy. 
 
+|`xmitHashPolicy`
+|`string`
+|Specifies the transmit hash policy for load balancing across the aggregated interfaces. This parameter defaults to `layer2` and supports the following values: `layer2`, `layer2+3` and `layer3+4`.
+
 |`linksInContainer`
 |`boolean`
 |Optional: Specifies whether the network interfaces intended for bonding are expected to be created and available directly within the container's network namespace when the bond starts. If `false` which is the default, the CNI plugin looks for these interfaces on the host system first before attempting to form the bond.
@@ -58,6 +62,11 @@ The following table describes the configuration parameters for the Bond CNI plug
 
 |====
 
+--
+:FeatureName: xmitHashPolicy
+include::snippets/technology-preview.adoc[]
+--
+
 [id="nw-multus-bond-cni-config-example_{context}"]
 == Bond CNI plugin configuration example
 
@@ -87,4 +96,35 @@ The following example configures a secondary network named `bond-net1`:
         "gateway": "10.56.217.1"
     }
 }
-----
+----
+
+The following example configures a secondary network named `bond-tlb-net` with the `xmitHashPolicy` feature enabled:
+
+[source,json]
+----
+{
+ "type": "bond",
+ "cniVersion": "0.3.1",
+ "name": "bond-tlb-net",
+ "mode": "tlb",         
+ "xmitHashPolicy": "layer2+3", <1>
+ "failOverMac": 0,         
+ "linksInContainer": true,
+ "miimon": "100",
+ "mtu": 1500,
+ "links": [
+       {"name": "net1"},
+       {"name": "net2"}
+   ],
+  "ipam": {
+        "type": "host-local",
+        "subnet": "10.57.218.0/24", 
+        "routes": [{
+        "dst": "0.0.0.0/0"
+        }],
+        "gateway": "10.57.218.1"
+    }
+}
+----
+
+<1> This parameter dictates how outgoing network traffic is distributed across the `net1` and `net2` active member interfaces within the bond. The hashing algorithm combines layer 2 information, specifically source and destination MAC addresses, with layer 3 information, which includes source and destination IP addresses.