Skip to content
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 1749468: UPSTREAM: 88734: Work-around for missing metrics on CRI-O exited containers #24653

Merged
merged 1 commit into from
Mar 11, 2020

Conversation

joelsmith
Copy link
Contributor

HPA needs metrics for exited init containers before it will
take action. By setting memory and CPU usage to zero for any
containers that cAdvisor didn't provide statistics for, we
are assured that HPA will be able to correctly calculate
pod resource usage.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 6, 2020
…ainers

HPA needs metrics for exited init containers before it will
take action. By setting memory and CPU usage to zero for any
containers that cAdvisor didn't provide statistics for, we
are assured that HPA will be able to correctly calculate
pod resource usage.
@openshift-ci-robot openshift-ci-robot added the vendor-update Touching vendor dir or related files label Mar 6, 2020
@joelsmith
Copy link
Contributor Author

FYI, upstream PR kubernetes/kubernetes#88734 has approval and lgtm, but can't merge because it's not tagged for the v1.18 milestone.

This is to address the bug https://bugzilla.redhat.com/show_bug.cgi?id=1749468
/cc @rphillips

@rphillips
Copy link
Contributor

/lgtm
/hold

holding for the upstream merge

@openshift-ci-robot openshift-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Mar 9, 2020
@rphillips
Copy link
Contributor

/assign @sjenning

@sjenning
Copy link
Contributor

sjenning commented Mar 9, 2020

PR is lgtm/approve upstream, just waiting for merge
/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelsmith, rphillips, sjenning

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 9, 2020
@joelsmith
Copy link
Contributor Author

Upstream just merged.
/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 10, 2020
@joelsmith
Copy link
Contributor Author

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit f2a9b7a into openshift:master Mar 11, 2020
@joelsmith
Copy link
Contributor Author

/cherrypick release-4.4

@openshift-cherrypick-robot

@joelsmith: new pull request created: #24671

In response to this:

/cherrypick release-4.4

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.

@rphillips
Copy link
Contributor

/retitle Bug 1749468: UPSTREAM: 88734: Work-around for missing metrics on CRI-O exited containers

@openshift-ci-robot openshift-ci-robot changed the title UPSTREAM: 88734: Work-around for missing metrics on CRI-O exited containers Bug 1749468: UPSTREAM: 88734: Work-around for missing metrics on CRI-O exited containers Mar 17, 2020
@openshift-ci-robot
Copy link

@joelsmith: All pull requests linked via external trackers have merged. Bugzilla bug 1749468 has been moved to the MODIFIED state.

In response to this:

Bug 1749468: UPSTREAM: 88734: Work-around for missing metrics on CRI-O exited containers

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.

@joelsmith
Copy link
Contributor Author

/cherrypick release-4.3

@openshift-cherrypick-robot

@joelsmith: new pull request created: #24860

In response to this:

/cherrypick release-4.3

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants