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 2094362: Duplicate prometheus rules for API SLOs after upgrade #1376
Bug 2094362: Duplicate prometheus rules for API SLOs after upgrade #1376
Conversation
sanchezl
commented
Sep 7, 2022
- use conditional static resource functionality
- delete prometheusrules/kube-apiserver-slos
@sanchezl: This pull request references Bugzilla bug 2094362, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/bugzilla refresh |
@sanchezl: This pull request references Bugzilla bug 2094362, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
kube-apiserver-slos was split into basic and extended in 4.9. Delete the kube-apiserver-slos resource on clusters that have been upgraded from 4.8.
36fe07e
to
0a83a4d
Compare
Any updates on the PR? It seems this issue is causing quite a lot of noise to be generated (both for our customers as well as on fleet level when analyzing the overall health of connected clusters) and fixing it would help us better focus on more severe issues. |
/retest-required |
1 similar comment
/retest-required |
/retest |
/bugzilla refresh |
@sanchezl: This pull request references Bugzilla bug 2094362, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, sanchezl, tkashem 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-required |
@sanchezl: The following tests 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/test-infra repository. I understand the commands that are listed here. |
@sanchezl: All pull requests linked via external trackers have merged: Bugzilla bug 2094362 has been moved to the MODIFIED state. 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. |
/cherry-pick release-4.11 |
@sanchezl: new pull request created: #1397 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. |