It seems that we have to live with this monstrosity until support for service-port ranges lands in Kubernetes. The only way we can deal with the fact that media servers use entire port ranges is to ignore the Service port in UDPRoutes. This, however, often confuses users (quite understandably).
For now, we have to make a better job at documenting the fact that we completely omit ports in UDPRoute backend Services.
It seems that we have to live with this monstrosity until support for service-port ranges lands in Kubernetes. The only way we can deal with the fact that media servers use entire port ranges is to ignore the Service port in UDPRoutes. This, however, often confuses users (quite understandably).
For now, we have to make a better job at documenting the fact that we completely omit ports in UDPRoute backend Services.