-
Notifications
You must be signed in to change notification settings - Fork 99
Bug 1905323: Request appropriate memory for dns-node-resolver container #225
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
Conversation
|
@rfredette: An error was encountered adding this pull request to the external tracker bugs for bug 1905323 on the Bugzilla server at https://bugzilla.redhat.com:
DetailsIn 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. |
|
/bugzilla refresh |
|
@sgreene570: An error was encountered adding this pull request to the external tracker bugs for bug 1905323 on the Bugzilla server at https://bugzilla.redhat.com:
DetailsIn 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. |
|
/bugzilla refresh |
|
@rfredette: This pull request references Bugzilla bug 1905323, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
DetailsIn 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. |
|
/retest |
|
/bugzilla cc-qa |
|
@lihongan: This pull request references Bugzilla bug 1905323, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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. |
|
@rfredette seems the dns-operator container also didn't include a memory request. could you have a double check? |
|
@lihongan you are correct, dns-operator is missing a memory request. I'll add that to this PR today. |
|
/test e2e-aws-operator |
1 similar comment
|
/test e2e-aws-operator |
|
@rfredette: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
@rfredette #226 will resolve the failures seen on e2e-aws-operator. |
|
/test e2e-aws-operator |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah, rfredette The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@rfredette: All pull requests linked via external trackers have merged: Bugzilla bug 1905323 has been moved to the MODIFIED state. DetailsIn 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. |
Cluster components are expected to request cpu & memory resources. dns-node-resolver already requested an amount of cpu time, but didn't include a memory request.
Following the guidelines here, I ran
make test-e2eagainst a cluster on AWS running a 4.7 nightly build. I queried prometheus for the metriccontainer_memory_usage_bytes{container="dns-node-resolver"}every 15 seconds between the start and finish of the e2e run, then I sorted the data points by memory usage to find the 90th percentile.I'm not sure why, but there was a spread of about 13MiB of memory used between different dns-node-resolver containers in the daemonset. Looking at all the containers as a single set, the 90th percentile memory usage was 11,239,424 bytes, but one of the individual containers had a 90th percentile memory usage of 19,963,904 bytes, or about 19MiB. I chose to use the 90th percentile number from the individual container.
Adding 10% overhead to that number produced 20.94MiB, which I rounded to 21MiB.