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
Other Ingress-likes (e.g. below our TCPIngress type) support multiple rules, which can target different Services:
spec:
rules:
- host: <SNI, optional>
port: <port on which to expose this service, required>
backend:
serviceName: <name of the kubernetes service, required>
servicePort: <port number to forward on the service, required>
The same is true for the Gateway TCPRoute spec. UDPRoute would presumably be similar.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The v1alpha1 UDPIngress supports a single rule only, represented by the entire spec:
Other Ingress-likes (e.g. below our TCPIngress type) support multiple rules, which can target different Services:
The same is true for the Gateway TCPRoute spec. UDPRoute would presumably be similar.
See also: #1080
The text was updated successfully, but these errors were encountered: