Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-569

AWS - Allocate Load Balancers (API & Ingress) to Specific Subnets

XMLWordPrintable

    • Product / Portfolio Work
    • OCPSTRAT-848Consistent Ingress/Egress into OpenShift clusters across providers
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

       

      Why is this important?

      Currently, when deploying an IngressController instance , all the FrontendIPs will be in the same subnet. However, the LoadBalancer Service implementation allows specifying the target subnet through service annotation. Therefore the need 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. 

      Scenarios

      If the cluster is spread across multiple subnets then its good to have a way to set subnet while creating ingresscontroller of type LoadBalancerService.

              ddharwar@redhat.com Deepthi Dharwar (Inactive)
              ddharwar@redhat.com Deepthi Dharwar (Inactive)
              None
              None
              Grant Spence Grant Spence (Inactive)
              Yunfei Jiang Yunfei Jiang
              Ashley Hardin Ashley Hardin
              Chris Fields Chris Fields
              Votes:
              1 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: