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

Customize loadbalancer type service for OCP ingress


    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Customize loadbalancer type service for OCP ingress
      2. What is the nature and description of the request?

      Provide some annotations that it only selects OCP ingress nodes and not all the nodes. 

      3. Why does the customer need this? (List the business requirements here)

      Current scenario: OCP on GCP uses Kubernetes service type LoadBalancer  for ingress vips, this ends up creating an instance group where all the nodes are added into this dynamically created instance group. This leaves no choice for us to use custom ingress for our cluster, we use istio ingress for our OCP clusters.  As we have requirement for these instance groups to listen on specific istio node port, we cant use the ones created by openshift [ also there would be too many unhealth members show up on LB as istio health check will only work for istio nodes]

      Now the only option that I am left with is to go to these dynamic instance group by OCP , remove all the istio nodes from instance groups and quickly create the istio Instance group [if not done quicly , Kubernetes add the istio nodes back to OCP instance groups]. This is a manual effort and post that we will start getting error on OCP side that its not able to add istio nodes in instance groups, which keep on flowing in the logs for ever.

      4. List any affected packages or components.

      Openshift 4.12


            ddharwar@redhat.com Deepthi Dharwar
            rhn-support-joeherna Joel Hernandez
            2 Vote for this issue
            5 Start watching this issue