Updated the stress/load test cases.#6942
Conversation
* Add values for config map settings, including access log. More docs. * Updates and improvements for the stress-testing configs.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: costinm The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
| labels: | ||
| name: ncli-fortio-noistio1 | ||
| app: acli-fortio-noistio1 | ||
| version: cli-fortio-noistio1 |
There was a problem hiding this comment.
shouldn't this have an annotation ?
There was a problem hiding this comment.
If it did - we would have no metrics (2 pods without istio sidecar calling each other). This way we generate outbound metrics ( and we find that they're not showing up in the dashboard - which is bug I need to file )
rshriram
left a comment
There was a problem hiding this comment.
would be good to have some script that adds/removes route rules periodically.
|
Yes, a job that runs a small script adding/removing routes would be great ! A bit busy getting the info/metrics about what went wrong during a push - would be great if someone can do it. |
More load, extra configs including tproxy.
Some builds are pinned to my build while they get into releases.