LoadBalancerRule API does not allow for tcp and udp to be selected as protocol. When a rule is created for a port choosing tcp as protocol, an additional rule cannot be created for udp and a error message stating conflicting rule is thrown.
as discussed with @nlindblo on list at users@ [1] this is different as expected or as portforwarding works, while portforwarding is really not more than loadbalancing over a single backend. I can live with calling this a bug or a feature but really think it should be working as the user asks. It cuts across the whole system right into the VR hence I mark it as major but the solution might be just in the VR scripts or even just in the DAO?!?
Since CloudStack uses haproxy as a loadbalancer which doesn't support UDP, it would be a good idea to remove the option from the UI as well as have checks in the backend haproxy/haproxy#62
@nlindblo since HAproxy which is internally used for load balancing does not support udp, an appropriate check has been added. There will only be a conflict in case of tcp rules on the same port.
@nlindblo per this fix, this is now going to be a feature request (if you still want it) I'm closing this. you can reopen, use an alternative to the internal lb or enter a new feature request (which will probably require atr least some functional research and spec effort)
Activity
DaanHoogland commented on Nov 19, 2020
as discussed with @nlindblo on list at users@ [1] this is different as expected or as portforwarding works, while portforwarding is really not more than loadbalancing over a single backend. I can live with calling this a bug or a feature but really think it should be working as the user asks. It cuts across the whole system right into the VR hence I mark it as major but the solution might be just in the VR scripts or even just in the DAO?!?
[1] https://lists.apache.org/thread.html/rd0e615913601cbdae59d04e32907e1e4b8c995222a31d214ab0fe201%40%3Cusers.cloudstack.apache.org%3E
davidjumani commented on Nov 23, 2020
Since CloudStack uses haproxy as a loadbalancer which doesn't support UDP, it would be a good idea to remove the option from the UI as well as have checks in the backend
haproxy/haproxy#62
davidjumani commented on Nov 24, 2020
Disabled UDP via #4501 && apache/cloudstack-primate#871
davidjumani commented on Dec 2, 2020
@nlindblo since HAproxy which is internally used for load balancing does not support udp, an appropriate check has been added. There will only be a conflict in case of tcp rules on the same port.
DaanHoogland commented on Dec 2, 2020
@nlindblo per this fix, this is now going to be a feature request (if you still want it) I'm closing this. you can reopen, use an alternative to the internal lb or enter a new feature request (which will probably require atr least some functional research and spec effort)