-
Bug
-
Resolution: Done
-
Normal
-
4.12
-
None
-
Critical
-
No
-
SDN Sprint 237
-
1
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-14635. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-13140. The following is the description of the original issue:
—
Description of problem:
According to the Red Hat documentation https://docs.openshift.com/container-platform/4.12/networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.html, the maximum number of IP aliases per node is 10 - "Per node, the maximum number of IP aliases, both IPv4 and IPv6, is 10.". Looking at the code base, the number of allowed IPs is calculated as Capacity = defaultGCPPrivateIPCapacity (which is set to 10) + cloudPrivateIPsCount (that is number of available IPs from the range) - currentIPv4Usage (number of assigned v4 IPs) - currentIPv6Usage (number of assigned v6 IPs) https://github.com/openshift/cloud-network-config-controller/blob/master/pkg/cloudprovider/gcp.go#L18-L22 Speaking to GCP, they support up to 100 alias IP ranges (not IPs) per vNIC. Can Red Hat confirm 1) If there is a limitation of 10 from OCP and why? 2) If there isn't a limit, what is the maximum number of egress IPs that could be supported per node?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Case: 03487893
It is one of the most highlighted bug from our customer.
- clones
-
OCPBUGS-14635 Maximum Number Of Egress IPs Supported
- Closed
- is blocked by
-
OCPBUGS-14635 Maximum Number Of Egress IPs Supported
- Closed
- links to