chaos-controller
chaos-controller copied to clipboard
Dogfood e2etest; Client/Server Application
What does this PR do?
- [X] Adds new functionality
- [ ] Alters existing functionality
- [ ] Fixes a bug
- [X] Improves documentation or testing
Please briefly describe your changes as well as the motivation behind them:
First iteration of a larger project to create regression-like testing for the chaos controller. The PR contains an updated dogfood which has been tweaked slightly to confirm that the metrics we need to test CPU, Network, and Disk are present in Datadog.
The tester folder is present in this PR to show the current path that will be taken with this project and is by no means done or being used in any capacity.
Code Quality Checklist
- [X] The documentation is up to date.
- [X] My code is sufficiently commented and passes continuous integration checks.
- [X] I have signed my commit (see Contributing Docs).
Testing
- [ ] I leveraged continuous integration testing
- [ ] by depending on existing
unittests orend-to-endtests. - [ ] by adding new
unittests orend-to-endtests.
- [ ] by depending on existing
- [x] I manually tested the following steps:
- [x] colima local testing with datadog agent deployed locally sending metrics to datadog
- [ ] locally.
- [ ] as a canary deployment to a cluster.
Note: we're keeping the PR open for now, we'll re-adapt it based on recent changes made to e2e tests plan once possible.