1. Proposed title of this feature request
Roundrobin LB algorithm to be used for `oauth-openshift` route.

2. What is the nature and description of the request?
Since the `oauth-openshift` route is created with the TLS termination `passthrough`. The default load balancing algorithm is always set `source` by default which means the same client IP always reaches the same server as long as no server goes down or up.
As we know if the PROXY PROTOCOL is not enabled on the ingresscontroller and the ingress load balancer, router pods will only see the ingress load balancer IP as the client IP and always redirect the request to the same `oauth-openshift` pod.

# Secure backend, pass through
backend be_tcp:openshift-authentication:oauth-openshift
  balance source

3. Why does the customer need this? (List the business requirements here)
Due to the `source` load balancing algorithm for this `passthrough` route, the remaining two `oauth-openshift `pods always stay idle and do not serve any requests. The requests to one of the remaining two oauth-openshift pods will only reach when the first `oauth-openshift` pod goes down and the hash result changes due to the changing number of running servers.

4. List any affected packages or components.
NetworkEdge, oauth