-
Notifications
You must be signed in to change notification settings - Fork 70
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
Update prombench/benchmark
manifests
#727
Update prombench/benchmark
manifests
#727
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems plausible.
Why do we have two configmaps for promtail that look very similar? |
Why is it running 3 promtails? This seems unnecessary. |
This one is to get the logs from each node via tha daemonset https://github.com/prometheus/test-infra/blob/master/prombench/manifests/cluster-infra/6d_promtail_daemon_set.yaml#L34 This promtail has two deployments because for when testing PR and One for testing against a Release. Is there a way to have this deployment conditonally? |
The DaemonSet only runs on one node, due to https://github.com/prometheus/test-infra/blob/master/prombench/manifests/cluster-infra/6d_promtail_daemon_set.yaml#L124 It’s unnecessary to have all this complication; I’ll fix it. |
I'll update it to the latest. |
71264d4
to
53e77ae
Compare
Rebased the PR |
53e77ae
to
785f447
Compare
e0a151d
to
f0fb1b5
Compare
Signed-off-by: Vandit Singh <[email protected]>
f0fb1b5
to
b8274b5
Compare
Solved the merge conflicts. gentle ping @bboreham |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Signed-off-by: Vandit Singh <[email protected]>
In this PR, I have
3.0.0