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
Fix deprecated use of watch API #6437
Conversation
Signed-off-by: Janusz Marcinkiewicz <januszm@nvidia.com>
Hi @VirrageS. Thanks for your PR. I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 |
/ok-to-test |
/retest |
1 similar comment
/retest |
/approve Nice small change. |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rmohr 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 |
1 similar comment
/retest |
What this PR does / why we need it: This MR fixes a problem that leads to reporting incorrect metrics in Kubernetes. The problem is that
watchFunc
uses deprecated (since K8s v1.12) API call which seems to be incorrectly interpreted byapiserver
. My fix is simply replacing old, deprecated method of indicating WATCH operation by a new one. After the fix theapiserver_request_duration_seconds
metrics for LIST operation drop to normal levels:Which issue(s) this PR fixes:
Fixes #6436
Special notes for your reviewer: None
Release note: