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
Copy file name to clipboardExpand all lines: docs/content/configuration.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,8 @@ The static configuration is configured when the service mesh is installed and is
21
21
22
22
- Access-Control List (ACL) mode can be enabled.
23
23
This configures Traefik Mesh to run in ACL mode, where all traffic is forbidden unless explicitly allowed via an SMI
24
-
[TrafficTarget](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-access/v1alpha2/traffic-access.md#traffictarget). Please see
25
-
the [SMI Specification](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-access/v1alpha2/traffic-access.md) for more information.
24
+
[TrafficTarget](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-access/v1alpha2/traffic-access.md#traffictarget). Please see
25
+
the [SMI Specification](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-access/v1alpha2/traffic-access.md) for more information.
26
26
27
27
## Dynamic configuration
28
28
@@ -55,8 +55,8 @@ If this annotation is not present, the mesh service will operate in the default
55
55
56
56
!!! Info
57
57
For now, the `udp` traffic type does not work when ACL mode is enabled. In ACL mode, all traffic is forbidden unless it
58
-
is explicitly allowed with a [TrafficTarget](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-access/v1alpha2/traffic-access.md#traffictarget) and
59
-
unfortunately the SMI specification does not yet define a [Traffic Spec](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-specs/v1alpha4/traffic-specs.md) for `UDP`.
58
+
is explicitly allowed with a [TrafficTarget](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-access/v1alpha2/traffic-access.md#traffictarget) and
59
+
unfortunately the SMI specification does not yet define a [Traffic Spec](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-specs/v1alpha4/traffic-specs.md) for `UDP`.
60
60
61
61
#### Scheme
62
62
@@ -141,7 +141,7 @@ More precisely, the `server` app is composed by two routes:
141
141
- The `api` route under the `/api` path, accepting all methods.
142
142
- The `metrics` routes under the `/metrics` path, accepting only `GET` requests.
143
143
144
-
Other types of route groups and detailed information are available [in the SMI specification](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-specs/v1alpha3/traffic-specs.md).
144
+
Other types of route groups and detailed information are available [in the SMI specification](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-specs/v1alpha3/traffic-specs.md).
145
145
146
146
By default, all traffic is denied so we need to grant access to clients to our application. This is done by defining a `TrafficTarget`.
147
147
@@ -177,7 +177,7 @@ In this example, we grant access to all pods running with the service account `c
177
177
178
178
Any client running with the service account `client` under the `client` namespace accessing `server.server.traefik.mesh/api` is allowed to access the `/api` resource. Others will receive 404 answers from the Traefik Mesh node.
179
179
180
-
More information can be found [in the SMI specification](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-access/v1alpha2/traffic-access.md).
180
+
More information can be found [in the SMI specification](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-access/v1alpha2/traffic-access.md).
181
181
182
182
#### Traffic Splitting
183
183
@@ -201,8 +201,8 @@ spec:
201
201
In this example, we define a traffic split for our server service between two versions of our server, v1 and v2.
202
202
`server.server.traefik.mesh`directs 80% of the traffic to the server-v1 pods, and 20% of the traffic to the server-v2 pods.
203
203
204
-
More information can be found [in the SMI specification](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-split/v1alpha3/traffic-split.md).
204
+
More information can be found [in the SMI specification](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-split/v1alpha3/traffic-split.md).
205
205
206
206
#### Traffic Metrics
207
207
208
-
At the moment, Traefik Mesh does not implement the [Traffic Metrics specification](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-metrics/v1alpha1/traffic-metrics.md).
208
+
At the moment, Traefik Mesh does not implement the [Traffic Metrics specification](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-metrics/v1alpha1/traffic-metrics.md).
Copy file name to clipboardExpand all lines: docs/content/examples.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ X-Forwarded-For: 3.4.5.6
247
247
## ACL Example
248
248
249
249
The [ACL mode](install.md#access-control-list) can be enabled when installing Traefik Mesh.
250
-
Once activated, all traffic is forbidden unless explicitly authorized using the SMI [TrafficTarget](https://github.com/servicemeshinterface/smi-spec/blob/master/apis/traffic-access/v1alpha2/traffic-access.md#traffictarget) resource.
250
+
Once activated, all traffic is forbidden unless explicitly authorized using the SMI [TrafficTarget](https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-access/v1alpha2/traffic-access.md#traffictarget) resource.
251
251
This example will present the configuration required to allow the client pod to send traffic to the HTTP and TCP services defined in the previous example.
252
252
253
253
Each `TrafficTarget` defines that a set of source `ServiceAccount` is capable of sending traffic to a destination `ServiceAccount`.
0 commit comments