You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: