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/gitbook/usage/how-it-works.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,14 +148,15 @@ spec:
148
148
targetPort: 9898
149
149
portDiscovery: true
150
150
headless: false
151
+
trafficDistribution: PreferClose
151
152
```
152
153
153
154
The container port from the target workload should match the `service.port` or `service.targetPort`.
154
155
The `service.name` is optional, defaults to `spec.targetRef.name`.
155
156
The `service.targetPort` can be a container port number or name.
156
157
The `service.portName` is optional (defaults to `http`), if your workload uses gRPC then set the port name to `grpc`.
157
158
The `service.appProtocol` is optional, more details can be found [here](https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol).
158
-
159
+
The `service.trafficDistribution` is optional, more details can be found [here](https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution).
159
160
160
161
If port discovery is enabled, Flagger scans the target workload and extracts the containers ports
161
162
excluding the port specified in the canary service and service mesh sidecar ports.
// Operation cannot be fulfilled on services "mysvc-canary": the object has been modified; please apply your changes to the latest version and try again
0 commit comments