New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move benchmark to remote write #313
Move benchmark to remote write #313
Conversation
cea5365
to
c7e1a3c
Compare
This commit migrates the Telemeter server benchmark tests from the Prometheus to the remote-write architecture. This will allow us to completely eliminate the Prometheus storage stack, including manifests and go code. Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
c7e1a3c
to
e8ef1d6
Compare
/ok-to-test |
/refresh |
unblocks: #271 |
/test e2e-aws |
This is failing because the benchmark test is not using the telemeter image built from the code in the PR. It is using We need to update the tests to use the telemeter image built from the source. |
/test e2e-aws |
/test benchmark |
/retest |
f02c8fa
to
3510575
Compare
Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
3510575
to
fbb6378
Compare
/retest |
/lgtm |
As a follow up, let's remove the prometheus operator dependency in the jsonnetfile, as this is not required anymore, coincidentally that will make bumping kube-prometheus a lot easier in cluster-monitoring-operator! 🎉 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brancz, squat The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR migrates the Telemeter server benchmark tests from the
Prometheus to the remote-write architecture. This will allow us to
completely eliminate the Prometheus storage stack, including manifests
and go code.