Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-13140

Maximum Number Of Egress IPs Supported

XMLWordPrintable

    • Critical
    • No
    • SDN Sprint 236, SDN Sprint 237
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      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.

       

              jluhrsen Jamo Luhrsen
              rhn-support-jpradhan Jitendra Pradhan
              Huiran Wang Huiran Wang
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: