Configuration for a bridge secondary network
The Bridge CNI plugin JSON configuration object describes the configuration parameters for the Bridge CNI plugin.
The following table details the configuration parameters:
| Field | Type | Description |
|---|---|---|
|
|
The CNI specification version. A minimum version of |
|
|
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. |
|
|
The name of the CNI plugin to configure: |
|
|
The configuration object for the IPAM CNI plugin. The plugin manages IP address assignment for the attachment definition. |
|
|
Optional: Specify the name of the virtual bridge to use. If the bridge interface does not exist on the host, the bridge interface gets created. The default value is |
|
|
Optional: Set to |
|
|
Optional: Controls the container interface ( |
|
|
Optional: Set to |
|
|
Optional: Set to |
|
|
Optional: Set to |
|
|
Optional: Set to |
|
|
Optional: Set to |
|
|
Optional: Specify a virtual LAN (VLAN) tag as an integer value. By default, no VLAN tag is assigned. |
|
|
Optional: Indicates whether the default VLAN must be preserved on the |
|
|
Optional: If |
|
|
Optional: Assign a VLAN trunk tag. The default value is |
|
|
Optional: Set the maximum transmission unit (MTU) to the specified value. The default value is automatically set by the kernel. |
|
|
Optional: Enables duplicate address detection for the container side |
|
|
Optional: Enables mac spoof check, limiting the traffic originating from the container to the mac address of the interface. The default value is |
|
|
The VLAN parameter configures the VLAN tag on the host end of the |
|
|
To configure an uplink for an L2 network, you must allow the VLAN on the uplink interface by using the following command:
|