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
Bug 1813221: jsonnet/telemeter: set cpu requests, unset limits #320
Bug 1813221: jsonnet/telemeter: set cpu requests, unset limits #320
Conversation
@s-urbaniak: This pull request references Bugzilla bug 1813221, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
requests: | ||
cpu: 10m | ||
cpu: 1m |
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.
is this enough?
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.
for kube-rbac-proxy, yes, i measured it on a local e2e prometheus dump
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.
ack, looks like this was set as the request for every container in the pod. Even thought it's just a request, I don't think it's enough for telemeter client
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
it looks like this PR is built on top of a very old parent commit, which is why the integration tests are failing. Plz rebase and the tests should start passing |
@squat hmm, this is based on the newest release-4.4 commit:
|
yes, doesn't matter :) the dependency used in integration tests in ALL branches moved and needs to be fixed. You need this PR: #317 |
/retest Please review the full test history for this PR and help us cut down flakes. |
ok, cherry-picked #317 commits, let's see how this goes. |
looks good to me but having @squat review the cherry-pick /lgtm |
To keep the backport as minimal as possible, let's drop commit bf34f2c, it's not needed |
ArchLinux recently moved to using zstd as compression algorithm. https://www.archlinux.org/news/now-using-zstandard-instead-of-xz-for-package-compression/
5d40ea6
to
f8e185f
Compare
@squat fixed, PTAL |
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.
looks mostly good to me, however I think 1m CPU request is undersized for the telemeter-client container
@squat telemeter-client container peaks at 0.3 millicores This is data taken from a e2e test run which we take as the reference. ptal |
excellent :) |
@squat or anybody out there, can i have a |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brancz, paulfantom, s-urbaniak, 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 |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
setting cherry-pick approval as this is a jsonnet library change only which will be vendored into cluster-monitoring-operator. |
@s-urbaniak: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @openshift/openshift-team-monitoring