// Module included in the following assemblies:
//
// * networking/multiple_networks/secondary_networks/creating-secondary-networks-other-cni.adoc
// * microshift_networking/microshift_multiple_networks/microshift_cni_multus.adoc

:_mod-docs-content-type: REFERENCE
[id="nw-multus-bridge-object_{context}"]
= Configuration for a bridge secondary network

[role="_abstract"]
The Bridge CNI plugin JSON configuration object describes the configuration parameters for the Bridge CNI plugin.

The following table details the configuration parameters:

[cols=".^2,.^2,.^6",options="header"]
|====
|Field|Type|Description

ifndef::microshift[]
|`cniVersion`
|`string`
|The CNI specification version. A minimum version of `0.3.1` is required.

|`name`
|`string`
|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[]
|`cniVersion`
|`string`
|The CNI specification version. The `0.4.0` value is required.
endif::microshift[]

|`type`
|`string`
|The name of the CNI plugin to configure: `bridge`.

|`ipam`
|`object`
|The configuration object for the IPAM CNI plugin. The plugin manages IP address assignment for the attachment definition.

|`bridge`
|`string`
|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 `cni0`.

|`ipMasq`
|`boolean`
|Optional: Set to `true` to enable IP masquerading for traffic that leaves the virtual network. The source IP address for all traffic is rewritten to the bridge's IP address. If the bridge does not have an IP address, this setting has no effect. The default value is `false`.

|`disableContainerInterface`
|`boolean`
|Optional: Controls the container interface (`veth` peer inside the `netns` container). When set to `true`, the container interface link-state is set to `down`, you cannot use the IPAM CNI plugin. The default value is `false`.

|`isGateway`
|`boolean`
|Optional: Set to `true` to assign an IP address to the bridge. The default value is `false`.

|`isDefaultGateway`
|`boolean`
|Optional: Set to `true` to configure the bridge as the default gateway for the virtual network. The assigned IP address of the bridge is used as the default route. If `isDefaultGateway` is set to `true`, `isGateway` is also set to `true` automatically. The default value is `false`.

|`forceAddress`
|`boolean`
|Optional: Set to `true` to allow assignment of a previously assigned IP address to the virtual bridge. When set to `false`, if an IPv4 address or an IPv6 address from overlapping subsets is assigned to the virtual bridge, an error occurs. The default value is `false`.

|`hairpinMode`
|`boolean`
|Optional: Set to `true` to allow the virtual bridge to send an Ethernet frame back through the virtual port it was received on. This mode is also known as _reflective relay_. The default value is `false`.

|`promiscMode`
|`boolean`
|Optional: Set to `true` to enable promiscuous mode on the bridge. The default value is `false`.

ifndef::microshift[]
|`vlan`
|`integer`
|Optional: Specify a virtual LAN (VLAN) tag as an integer value. By default, no VLAN tag is assigned.

|`preserveDefaultVlan`
|`boolean`
|Optional: Indicates whether the default VLAN must be preserved on the `veth` end connected to the bridge. Defaults to `false`.

|`portIsolation`
|`boolean`
|Optional: If `true`, prevents containers on the same bridge from communicating with each other. A container can still reach non-isolated ports. For example, a bridge interface that allows access to the host or an optional uplink that allows access outside the host. The default value is `false`.

|`vlanTrunk`
|`list`
|Optional: Assign a VLAN trunk tag. The default value is `none`.
endif::microshift[]

|`mtu`
|`integer`
|Optional: Set the maximum transmission unit (MTU) to the specified value. The default value is automatically set by the kernel.

|`enabledad`
|`boolean`
|Optional: Enables duplicate address detection for the container side `veth`. The default value is `false`.

|`macspoofchk`
|`boolean`
|Optional: Enables mac spoof check, limiting the traffic originating from the container to the mac address of the interface. The default value is `false`.
|====

ifndef::microshift[]
[NOTE]
====
The VLAN parameter configures the VLAN tag on the host end of the `veth` and also enables the `vlan_filtering` feature on the bridge interface.
====

[NOTE]
====
To configure an uplink for an L2 network, you must allow the VLAN on the uplink interface by using the following command:

[source,terminal]
----
$  bridge vlan add vid VLAN_ID dev DEV
----
====

[id="nw-multus-bridge-config-example_{context}"]
== Bridge CNI plugin configuration example

The following example configures a secondary network named `bridge-net`:

[source,json]
----
{
  "cniVersion": "0.3.1",
  "name": "bridge-net",
  "type": "bridge",
  "isGateway": true,
  "vlan": 2,
  "ipam": {
    "type": "dhcp"
    }
}
----
endif::microshift[]

ifdef::microshift[]
[id="microshift-nw-multus-bridge-config-example_{context}"]
== Bridge CNI plugin configuration example

The following example configures a secondary network named `bridge-conf` for use with the {microshift-short} Multus CNI:

[source,json,subs="verbatim"]
----
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: bridge-conf
spec:
  config: '{
      "cniVersion": "0.4.0",
      "type": "bridge",
      "bridge": "test-bridge",
      "mode": "bridge",
      "ipam": {
        "type": "host-local",
        "ranges": [
          [
            {
              "subnet": "10.10.0.0/16",
              "rangeStart": "10.10.1.20",
              "rangeEnd": "10.10.3.50",
              "gateway": "10.10.0.254"
            }
          ]
        ],
        "dataDir": "/var/lib/cni/test-bridge"
      }
    }'
----
endif::microshift[]
