Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5222

[METALLB] Increase the number to 4 on the avoidBuggyIPs parameter in the IPAddressPools

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • openshift-4.12.z, openshift-4.13.z, openshift-4.14.z, openshift-4.15.z
    • SDN
    • None
    • False
    • None
    • False
    • Not Selected
    • x86_64
    • 0
    • 0% 0%

      1. Proposed title of this feature request
      Increase the number to 4 IPs on the avoidBuggyIPs parameter in the IPAddressPools

      2. What is the nature and description of the request?
      At the moment when avoidBuggyIPs is set to true, the metallb controller calculates the allocation of the IPs to avoid IPs terminating in '.0' and '.255'. Even though this is great, in the overwhelming majority of cases IPs terminating in '.1' and '.254' are used for the network gateway IP and taking that in consideration I was wondering if we could change the calculation to remove 4 IPs from the network [1].

      Otherwise in these cases customer needs to always use manual allocation in order to avoid such IPs. And for customers that don't have this problem, they can always use the default which has avoidBuggyIPs set to false.

      [1] https://github.com/openshift/metallb/blob/feb0c051c265e8d9e1c4ba1989d5f122517f00e4/internal/allocator/allocator.go#L451

      3. Why does the customer need this? (List the business requirements here)
      In most cases IPs terminating in .1 and .254 are used for the gateway IPs of the respective network.

      4. List any affected packages or components.
      MetalLb Controller

            mcurry@redhat.com Marc Curry
            rhn-support-andcosta Andre Costa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: