-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14, 4.16, 4.18, 4.20
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Some customers/Partners need to set cluster network MTU at deployment time using ZTP/GitOps in order to specify cluster network within extra MTU buffer to avoid future MTU update in day2 (MTU update in day2 require a minimum of 2 reboots). Today MTU is define by cluster network operator at deployment time based on MTU configured on machine network interface. By setting the cluster network MTU at deployment time, CNO will set this value instead of calculate/define cluster network MTU value based on machine network MTU (cluster network MTU must be lower than machine network MTU by 100 bytes (ovn overhead) if ipsec not enabled). We do not have in ZTP/GitOps (edge computing) or Telco Core RDS documentation, a note explaining how to set this cluster network MTU as for machine network MTU at deployment time. We wrote a KB article for the procedure: https://access.redhat.com/node/7134465/draf as reference.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: