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: charts/loadtester/Chart.yaml
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
apiVersion: v1
2
2
name: loadtester
3
-
version: 0.30.0
4
-
appVersion: 0.30.0
3
+
version: 0.31.0
4
+
appVersion: 0.31.0
5
5
kubeVersion: ">=1.19.0-0"
6
6
engine: gotpl
7
7
description: Flagger's load testing services based on rakyll/hey and bojand/ghz that generates traffic during canary analysis when configured as a webhook.
Copy file name to clipboardExpand all lines: docs/gitbook/tutorials/istio-progressive-delivery.md
+7-9
Original file line number
Diff line number
Diff line change
@@ -508,15 +508,13 @@ spec:
508
508
```yaml
509
509
apiVersion: flagger.app/v1beta1
510
510
kind: Canary
511
-
...
512
-
...
513
-
service:
514
-
port: 7070
515
-
appProtocol: TCP # <== set the appProtocol here
516
-
targetPort: 7070
517
-
portName: "tcp-service-port"
518
-
...
519
-
...
511
+
# omitted for brevity
512
+
spec:
513
+
service:
514
+
port: 7070
515
+
appProtocol: TCP # <== set the appProtocol here
516
+
targetPort: 7070
517
+
portName: "tcp-service-port"
520
518
```
521
519
522
520
If the `appProtocol` equals `TCP` then Flagger will treat this as a Canary deployment for a `TCP` service. When it creates the `VirtualService` document it will add a `TCP` section to route requests between the `primary` and `canary` services. See Istio documentation for more information on this [spec](https://istio.io/latest/docs/reference/config/networking/virtual-service/#TCPRoute).
0 commit comments