*ks: correctly define cluster:node_cpu:ratio rule #1520
Conversation
There was a bug in the rule imported from kube-prometheus causing the rule not to correctly return any results. This caused the data to be missing on the optimized dashboard from *ks clusters. Upstream fix was here: prometheus-operator/kube-prometheus#1628 Signed-off-by: Jacob Baungard Hansen <jacobbaungard@redhat.com>
|
|
/test e2e-kind |
|
@jacobbaungard: The following test failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jacobbaungard, thibaultmg 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 |
|
/cherrypick release-2.10 |
|
@jacobbaungard: once the present PR merges, I will cherry-pick it on top of release-2.10 in a new PR and assign it to you. 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-sigs/prow repository. |
|
@jacobbaungard: new pull request created: #1521 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-sigs/prow repository. |
There was a bug in the rule imported from kube-prometheus causing the rule not to correctly return any results. This caused the data to be missing on the optimized dashboard from *ks clusters. Upstream fix was here: prometheus-operator/kube-prometheus#1628 Signed-off-by: Jacob Baungard Hansen <jacobbaungard@redhat.com>
There was a bug in the rule imported from kube-prometheus causing the rule not to correctly return any results. This caused the data to be missing on the optimized dashboard from *ks clusters.
Upstream fix was here:
prometheus-operator/kube-prometheus#1628