Mixed protocol is not supported for LoadBalancer service for AWS in RHOCP 4

Solution Verified - Updated -

Issue

  • When attempting to configure a LoadBalancer service to handle both UDP and TCP traffic, the service-controller fails with the error mixed protocol is not supported for LoadBalancer:

    $ oc describe svc <mixed-protocol-service> -n <NAMESPACE>
    [...]
    Type:                     LoadBalancer
    
    Port:                     tcp-port  80/TCP
    TargetPort:               8080/TCP
    NodePort:                 tcp-port  32512/TCP
    Endpoints:                x.x.x.x:8080
    Port:                     udp-port  81/UDP
    TargetPort:               8081/UDP
    NodePort:                 udp-port  31702/UDP
    [...]
    Events:
     Type     Reason                  Age                From                Message
     ----     ------                  ----               ----                -------
     Normal   EnsuringLoadBalancer    43s (x8 over 10m)  service-controller  Ensuring load balancer
     Warning  SyncLoadBalancerFailed  43s (x8 over 10m)  service-controller  Error syncing load balancer: failed to ensure load balancer: mixed protocol is not supported for LoadBalancer
    
    

    Service remains in pending state:

    $ oc get svc <mixed-protocol-service> -n <NAMESPACE>
    NAME                       TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)                     AGE
    <mixed-protocol-service>   LoadBalancer   y.y.y.y        <pending>     80:32512/TCP,81:31702/UDP   
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content