NO-JIRA: sizing: add logging for what we're doing #3961
Conversation
The logical flows in the request serving node component scheduler and sizer are complex; we need a little more insight into what decisions we're taking, when, and why. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@stevekuznetsov: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
area/hypershift-operator
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csrwng, stevekuznetsov 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 |
openshift-ci
bot
added
the
approved
|
/lgtm |
|
@stevekuznetsov: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
The logical flows in the request serving node component scheduler and sizer are complex; we need a little more insight into what decisions we're taking, when, and why.
/assign @csrwng