Release staleness testing
Open
@cpretzer is already working on this.
Since Mar 30, 2020.
area/test
priority/P0
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
Staleness has been an issue off and on for the last release. In preparation for the upcoming stable release, let's do some extended testing to verify that staleness isn't an issue.
At a high level, this should be:
- Install a demo application on the cluster, add it to the data plane.
- Add service profiles for this demo application.
- Pause load for 10+ minutes
- Leave the load generator alone
- Update all the load targets so that there are new pods.
- Verify that there are no 5xx errors.
Please write up the results and methodology used for this test. Some graphs of the usage from each test would be much appreciated (success, latency, throughput, resource usage).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.