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

OCPBUGS-27445: Use cached clients to avoid client side throttling #656

Merged

Conversation

fxierh
Copy link
Contributor

@fxierh fxierh commented Jan 21, 2024

Client-side throttling was observed after switching to the live client in the metrics controller in #645.

This PR:

  • Adds a (cached) root client to the Calculator struct for querying the root credential only.
  • Switches back to the default (cached) client (i.e. mgr.GetClient()) for querying anything else.

Signed-off-by: Feilian Xie <fxie@redhat.com>
…e root credential only

Signed-off-by: Feilian Xie <fxie@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 21, 2024
@openshift-ci-robot
Copy link
Contributor

@fxierh: This pull request references Jira Issue OCPBUGS-27445, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Client-side throttling was observed after switching to the live client in the metrics controller in #645.

This PR:

  • Adds a (cached) root client to the Calculator struct for querying the root credential only.
  • Switches back to the default (cached) client (i.e. mgr.GetClient()) for querying anything else.

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.

@fxierh
Copy link
Contributor Author

fxierh commented Jan 21, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 21, 2024
@openshift-ci-robot
Copy link
Contributor

@fxierh: This pull request references Jira Issue OCPBUGS-27445, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianping-shu

In response to this:

/jira refresh

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.

@fxierh
Copy link
Contributor Author

fxierh commented Jan 21, 2024

/hold

Work in progress.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2024
Copy link

codecov bot commented Jan 21, 2024

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (9924b77) 48.34% compared to head (7c4f0b5) 48.34%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #656      +/-   ##
==========================================
- Coverage   48.34%   48.34%   -0.01%     
==========================================
  Files          96       96              
  Lines       11780    11781       +1     
==========================================
  Hits         5695     5695              
- Misses       5452     5453       +1     
  Partials      633      633              
Files Coverage Δ
pkg/operator/metrics/metrics.go 45.16% <33.33%> (-0.25%) ⬇️

@fxierh
Copy link
Contributor Author

fxierh commented Jan 21, 2024

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 21, 2024
@fxierh fxierh changed the title OCPBUGS-27445: WIP: Use cached clients to avoid client side throttling OCPBUGS-27445: Use cached clients to avoid client side throttling Jan 21, 2024
@fxierh
Copy link
Contributor Author

fxierh commented Jan 21, 2024

/assign @jstuever @dlom

Would you please take a look ? Thanks.

Copy link
Contributor

@jstuever jstuever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@jstuever
Copy link
Contributor

/override ci/prow/security

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 24, 2024
Copy link
Contributor

openshift-ci bot commented Jan 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fxierh, jstuever

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 24, 2024
Copy link
Contributor

openshift-ci bot commented Jan 24, 2024

@jstuever: Overrode contexts on behalf of jstuever: ci/prow/security

In response to this:

/override ci/prow/security

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.

Copy link
Contributor

openshift-ci bot commented Jan 24, 2024

@fxierh: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit ba16998 into openshift:master Jan 24, 2024
11 checks passed
@openshift-ci-robot
Copy link
Contributor

@fxierh: Jira Issue OCPBUGS-27445: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27445 has been moved to the MODIFIED state.

In response to this:

Client-side throttling was observed after switching to the live client in the metrics controller in #645.

This PR:

  • Adds a (cached) root client to the Calculator struct for querying the root credential only.
  • Switches back to the default (cached) client (i.e. mgr.GetClient()) for querying anything else.

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.

@jstuever
Copy link
Contributor

/cherry-pick release-4.15

@openshift-cherrypick-robot

@jstuever: new pull request created: #660

In response to this:

/cherry-pick release-4.15

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants