Skip to content
This repository was archived by the owner on Oct 20, 2023. It is now read-only.

Commit c8bc04b

Browse files
committed
Fix formatting
Signed-off-by: stefanprodan <[email protected]>
1 parent 8008055 commit c8bc04b

File tree

2 files changed

+11
-8
lines changed

2 files changed

+11
-8
lines changed

apis/traffic-access/traffic-access-WD.md

+7-6
Original file line numberDiff line numberDiff line change
@@ -94,8 +94,9 @@ This example selects all the pods which have the `service-a` `ServiceAccount`.
9494
Traffic destined on a path `/metrics` is allowed. The `matches` field is
9595
optional and if omitted, a rule is valid for all the matches in a traffic spec
9696
(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
99100
will be allowed to all ports on the destination service.
100101

101102
Allowing destination traffic should only be possible with permission of the
@@ -195,8 +196,8 @@ The previous example would allow the following HTTP traffic:
195196

196197
## Example implementation for L4
197198

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.
200201

201202
```yaml
202203
kind: TCPRoute
@@ -237,8 +238,8 @@ spec:
237238
namespace: default
238239
```
239240

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`.
242243

243244
## Tradeoffs
244245

apis/traffic-specs/traffic-specs-WD.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,8 @@ spec:
150150
- 6446
151151
```
152152

153-
When matching ports are not specified, the TCP route will match all the ports of a Kubernetes service:
153+
When matching ports are not specified,
154+
the TCP route will match all the ports of a Kubernetes service:
154155

155156
```yaml
156157
kind: TCPRoute
@@ -176,7 +177,8 @@ spec:
176177
- 990
177178
```
178179

179-
When matching ports are not specified, the UDP route will match all the ports of a Kubernetes service:
180+
When matching ports are not specified,
181+
the UDP route will match all the ports of a Kubernetes service:
180182

181183
```yaml
182184
kind: UDPRoute

0 commit comments

Comments
 (0)