mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Merge pull request #104182 from openshift-cherrypick-robot/cherry-pick-102078-to-enterprise-4.21
[enterprise-4.21] OCPBUGS-59577 Correcting inaccurate description
This commit is contained in:
@@ -18,7 +18,7 @@ The following table describes the configuration parameters for the Bond CNI plug
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|Specifies the name given to this CNI network attachment definition. This name is used to identify and reference the interface within the container.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`cniVersion`
|
||||
|`string`
|
||||
@@ -34,7 +34,7 @@ The following table describes the configuration parameters for the Bond CNI plug
|
||||
|
||||
|`mtu`
|
||||
|`integer`
|
||||
|Optional: Specifies the maximum transmission unit (MTU) of the bond. The default is `1500`.
|
||||
|Optional: Specifies the maximum transmission unit (MTU) of the bond. The default is `1500`.
|
||||
|
||||
|`failOverMac`
|
||||
|`integer`
|
||||
@@ -42,7 +42,7 @@ The following table describes the configuration parameters for the Bond CNI plug
|
||||
|
||||
|`mode`
|
||||
|`string`
|
||||
|Specifies the bonding policy.
|
||||
|Specifies the bonding policy.
|
||||
|
||||
|`xmitHashPolicy`
|
||||
|`string`
|
||||
@@ -73,15 +73,15 @@ The following example configures a secondary network named `bond-net1`:
|
||||
[source,json]
|
||||
----
|
||||
{
|
||||
"type": "bond",
|
||||
"type": "bond",
|
||||
"cniVersion": "0.3.1",
|
||||
"name": "bond-net1",
|
||||
"mode": "active-backup",
|
||||
"failOverMac": 1,
|
||||
"linksInContainer": true,
|
||||
"mode": "active-backup",
|
||||
"failOverMac": 1,
|
||||
"linksInContainer": true,
|
||||
"miimon": "100",
|
||||
"mtu": 1500,
|
||||
"links": [
|
||||
"links": [
|
||||
{"name": "net1"},
|
||||
{"name": "net2"}
|
||||
],
|
||||
@@ -104,9 +104,9 @@ The following example configures a secondary network named `bond-tlb-net` with t
|
||||
"type": "bond",
|
||||
"cniVersion": "0.3.1",
|
||||
"name": "bond-tlb-net",
|
||||
"mode": "tlb",
|
||||
"xmitHashPolicy": "layer2+3", <1>
|
||||
"failOverMac": 0,
|
||||
"mode": "tlb",
|
||||
"xmitHashPolicy": "layer2+3",
|
||||
"failOverMac": 0,
|
||||
"linksInContainer": true,
|
||||
"miimon": "100",
|
||||
"mtu": 1500,
|
||||
@@ -116,7 +116,7 @@ The following example configures a secondary network named `bond-tlb-net` with t
|
||||
],
|
||||
"ipam": {
|
||||
"type": "host-local",
|
||||
"subnet": "10.57.218.0/24",
|
||||
"subnet": "10.57.218.0/24",
|
||||
"routes": [{
|
||||
"dst": "0.0.0.0/0"
|
||||
}],
|
||||
@@ -125,6 +125,6 @@ The following example configures a secondary network named `bond-tlb-net` with t
|
||||
}
|
||||
----
|
||||
|
||||
where
|
||||
|
||||
`xmitHashPolicy`:: 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.
|
||||
|
||||
* `xmitHashPolicy`: 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.
|
||||
|
||||
@@ -21,7 +21,8 @@ ifndef::microshift[]
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter you provided previously for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
endif::microshift[]
|
||||
|
||||
ifdef::microshift[]
|
||||
|
||||
@@ -21,7 +21,7 @@ The dummy device CNI plugin JSON configuration object describes the configuratio
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter that you previously specified for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`type`
|
||||
|`string`
|
||||
|
||||
@@ -26,7 +26,7 @@ The following table details the configuration parameters:
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter you provided previously for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`type`
|
||||
|`string`
|
||||
|
||||
@@ -23,7 +23,7 @@ The IPVLAN CNI plugin JSON configuration object describes the configuration para
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter you provided previously for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`type`
|
||||
|`string`
|
||||
|
||||
@@ -20,7 +20,7 @@ The MACVLAN CNI plugin JSON configuration object describes the configuration par
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter you provided previously for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`type`
|
||||
|`string`
|
||||
|
||||
@@ -19,7 +19,7 @@ The TAP CNI plugin JSON configuration object describes the configuration paramet
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter you provided previously for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`type`
|
||||
|`string`
|
||||
|
||||
@@ -21,7 +21,7 @@ The VLAN CNI plugin JSON configuration object describes the configuration parame
|
||||
|
||||
|`name`
|
||||
|`string`
|
||||
|The value for the `name` parameter you provided previously for the CNO configuration.
|
||||
|The mandatory, unique identifier assigned to this CNI network attachment definition. It is used by the container runtime to select the correct network configuration and serves as the key for persistent resource state management, such as IP address allocations.
|
||||
|
||||
|`type`
|
||||
|`string`
|
||||
|
||||
Reference in New Issue
Block a user