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: walkthroughs/howto-k8s-appmesh-load-test/README.md
+21-6Lines changed: 21 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,12 +35,27 @@ export VPC_ID=<VPC ID of the cluster, can be found using: aws eks describe-clus
35
35
## Step 3: Configuring the Load Test
36
36
All parameters of the mesh, load tests, metrics can be specified in `config.json`
37
37
38
-
`backends_map` -: The mapping from each Virtual Node to its backend Virtual Services. For each unique node name in `backends_map`,
39
-
a VirtualNode, Deployment, Service and VirtualService (with its VirtualNode as its target) are created at runtime.
40
-
41
-
`load_tests` -: Array of different test configurations that need to be run on the mesh. `url` is the service endpoint that Fortio (load generator) should hit.
42
-
43
-
`metrics` -: Map of metric_name to the corresponding metric PromQL logic
38
+
*`backends_map` -: The mapping from each Virtual Node to its backend Virtual Services. For each unique node name in `backends_map`,
39
+
a VirtualNode, Deployment, Service and VirtualService (with its VirtualNode as its target) are created at runtime. An example `backends_map` is following:
40
+
```
41
+
"backends_map": {
42
+
"0": ["1", "2"],
43
+
"1": ["3"],
44
+
"2": ["4"]
45
+
},
46
+
```
47
+
where the node names are `"0"`, `"1"`, `"2"`, `"3"` and `"4"`.
48
+
49
+
*`load_tests` -: Array of different test configurations that need to be run on the mesh.
50
+
*`url`: is the service endpoint that Fortio (load generator) should hit. The `url` format is: `http://service-<virtual-node-name>.tls-e2e.svc.cluster.local:9080/`.
51
+
For example, based on the above `backends_map`, if we want to send the load traffic to the first virtual node `"0"`, then the `ulr` will look like:
0 commit comments