-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14, 4.15, 4.16, 4.17, 4.18, 4.19, 4.20, 4.21
-
None
Description of problem:
The documentation doesn't have a strong warning about the impossibility of changing MTU at Day2, but just says: > For optimal network performance, you are using a network maximum transmission unit (MTU) of 9000 or greater on the OpenShift Container Platform cluster that hosts the KubeVirt virtual machines. If you use a lower MTU setting, network latency and the throughput of the hosted pods are affected. Enable multiqueue on node pools only when the MTU is 9000 or greater.
Version-Release number of selected component (if applicable):
4.14+
How reproducible:
Always
Steps to Reproduce:
1. Check the [0] documentation
2. Check the [1] KCS
3.
Actual results:
Customers are unaware and proceed by installing with default parameters, only to have it to be reinstalled if the issue arise later on
Expected results:
The doc should have a strong WARNING statement about this
Additional info:
[0] https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/hosted_control_planes/deploying-hosted-control-planes [1] https://access.redhat.com/solutions/7130660