-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Validate serviceNodePortRange value
2. What is the nature and description of the request?
After analyzing the issue reported in OCPBUGS-77769, OVN-K uses 'net.ipv4.ip_local_port_range' for egress SNAT operations in OVN. This range should not collide with the node port range being used in Kubernetes.
commit d31d1717da84a98b8feb08c261ec36c10cb416c5
On the other hand, as an overlap can also be introduced by setting sysctl 'net.ipv4.ip_local_port_range' , we should also monitor that there isn't overlap between 'serviceNodePortRange' and 'net.ipv4.ip_local_port_range' and send an alert if overlap is detected.
3. Why does the customer need this? (List the business requirements here)
If serviceNodePortRange value overlaps 'net.ipv4.ip_local_port_range' , this causes intermittent external connectivity issues
4. List any affected packages or components.
OVN-Kubernetes