Channels
#general
Title
c
careful-appointment-9763
05/03/2023, 6:04 PMTrying to resolve error "Error syncing load balancer: failed to ensure load balancer: mixed protocol is not supported for LoadBalancer". We need Port 5060 UDP and TCP on the same load balancer IP
c
creamy-pencil-82913
05/03/2023, 6:07 PMc
careful-appointment-9763
05/03/2023, 6:07 PMRancher v2.7.3
Provider: RKE2
Kubernetes Version: v1.25.9 +rke2r1
on AWS EC2 using Network Load Balancer
c
creamy-pencil-82913
05/03/2023, 6:07 PMNote: The set of protocols that can be used for LoadBalancer type of Services is still defined by the cloud provider. If a cloud provider does not support mixed protocols they will provide only a single protocol.
I don’t think AWS supports that
c
careful-appointment-9763
05/03/2023, 6:08 PMthey do
c
creamy-pencil-82913
05/03/2023, 6:08 PMthen you should check how to enable it in their controller config
because it is telling you that it does not
c
careful-appointment-9763
05/03/2023, 6:08 PMThis error isn't due to the feature gate?
c
creamy-pencil-82913
05/03/2023, 6:09 PMnot if you’re on 1.25, since as the docs page mentions it is on by default since 1.24
c
careful-appointment-9763
05/03/2023, 6:12 PMc
creamy-pencil-82913
05/03/2023, 6:12 PMyep
that was my recollection
AWS itself may allow it but the controller does not
c
careful-appointment-9763
05/03/2023, 6:13 PMhttps://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2759
Suggests a self-managed NLB
😞
This is all making me re-think containerized VoIP in general
178 Views