Merge pull request #20184 from MrSuicideParrot/main

[CI:DOCS] Add documentation for the vrf option on Netavark
This commit is contained in:
OpenShift Merge Robot 2023-09-28 07:53:52 -04:00 committed by GitHub
commit 8fb719fd04
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions

View File

@ -115,6 +115,7 @@ Additionally the `bridge` driver supports the following options:
- `isolate`: This option isolates networks by blocking traffic between those that have this option enabled. - `isolate`: This option isolates networks by blocking traffic between those that have this option enabled.
- `com.docker.network.bridge.name`: This option assigns the given name to the created Linux Bridge - `com.docker.network.bridge.name`: This option assigns the given name to the created Linux Bridge
- `com.docker.network.driver.mtu`: Sets the Maximum Transmission Unit (MTU) and takes an integer value. - `com.docker.network.driver.mtu`: Sets the Maximum Transmission Unit (MTU) and takes an integer value.
- `vrf`: This option assigns a VRF to the bridge interface. It accepts the name of the VRF and defaults to none. Can only be used with the Netavark network backend.
The `macvlan` and `ipvlan` driver support the following options: The `macvlan` and `ipvlan` driver support the following options: