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

Add ability to choose subnet while creating ingresscontroller of type LoadBalancerService

    XMLWordPrintable

Details

    • False
    • False
    • 0
    • 0% 0%
    • Undefined

    Description

      1. Proposed title of this feature request
      Add ability to choose subnet while creating ingresscontroller of type LoadBalancerService. Checking ingresscontroller CRD could see that there is no such way to set subnet of load balancer.

      2. What is the nature and description of the request?
      If the cluster is spread across multiple subnets then its good to have a way to set subnet while creating ingresscontroller of type LoadBalancerService.

      3. Why does the customer need this? (List the business requirements here)
      Currently, when deploying an IngressController instance , all the FrontendIPs will be in the same subnet. However, the LoadBalancer Service implementation allows to specify the target subnet through service annotation.

      We therefor propose to introduce an additional field to the ingresscontroller CRD, that allows to specify the target subnet.
      The value of this field is then used to annotate the created LoadBalancer Service from the beginning on, so the ingress controller immediately gets its FrontendIP into the right subnet.

      4. List any affected packages or components.
      Ingresscontroller

      Attachments

        Activity

          People

            mcurry@redhat.com Marc Curry
            rhn-support-arghosh Arnab Ghosh
            Votes:
            2 Vote for this issue
            Watchers:
            25 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: