-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
Description of problem:
Our current examples of OVN Kubernetes secondary networks have 2 MTU-related issues: 1. The layer 2 overlay example uses MTU 1300, although with default it could go up to 1400. Since many customers simply copy-paste documented examples, we should either use the typical maximum in the docs, or to remove this MTU field altogether and rely on OVN's default, which is 1400. 2. The localnet topology example does not specify any MTU. Due to that, it defaults to 1400, which is wasteful for localnet, since it can go (in the typical setup) up to 1500.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Docs
Steps to Reproduce:
1. Go to https://docs.openshift.com/container-platform/4.16/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html
Actual results:
"Creating a NAD for layer 2 topology using the CLI" mentions MTU 1300. "Creating a NAD for localnet topology using the CLI" mentions no MTU.
Expected results:
"Creating a NAD for layer 2 topology using the CLI" mentions MTU 1400 or nothing. "Creating a NAD for localnet topology using the CLI" mentions MTU 1500.
Additional info:
- duplicates
-
OCPBUGS-57322 Default MTU when using NADs is not 1300
-
- Closed
-
- is related to
-
CNV-68270 [CLOSED LOOP for] Document better MTU defaults for OVN Kubernetes
-
- New
-
- relates to
-
CNV-68331 Validate CNV-46504 - Document better MTU defaults for OVN Kubernetes
-
- New
-
- links to
(6 links to)