@@ -94,8 +94,9 @@ This example selects all the pods which have the `service-a` `ServiceAccount`.
94
94
Traffic destined on a path `/metrics` is allowed. The `matches` field is
95
95
optional and if omitted, a rule is valid for all the matches in a traffic spec
96
96
(a OR relationship). It is possible for a service to expose multiple ports,
97
- the TCPRoute/UDPRoute `matches.ports` field allows the user to specify specifically which port traffic
98
- should be allowed on. The `matches.ports` is an optional element, if not specified, traffic
97
+ the TCPRoute/UDPRoute `matches.ports` field allows the user to specify
98
+ specifically which port traffic should be allowed on.
99
+ The `matches.ports` is an optional element, if not specified, traffic
99
100
will be allowed to all ports on the destination service.
100
101
101
102
Allowing destination traffic should only be possible with permission of the
@@ -195,8 +196,8 @@ The previous example would allow the following HTTP traffic:
195
196
196
197
# # Example implementation for L4
197
198
198
- The following implementation how to define TrafficTargets for allowing TCP and UDP
199
- traffic to specific ports.
199
+ The following implementation shows how to define TrafficTargets for
200
+ allowing TCP and UDP traffic to specific ports.
200
201
201
202
` ` ` yaml
202
203
kind: TCPRoute
@@ -237,8 +238,8 @@ spec:
237
238
namespace: default
238
239
` ` `
239
240
240
- Note that the above configuration will allow TCP and UDP traffic to both `8301` and `8302` ports,
241
- but will block UDP traffic to `8300`.
241
+ Note that the above configuration will allow TCP and UDP traffic to
242
+ both `8301` and `8302` ports, but will block UDP traffic to `8300`.
242
243
243
244
# # Tradeoffs
244
245
0 commit comments