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

Add flag for changing rps limit in istioctl bug-report #40725

Merged
merged 3 commits into from
Sep 23, 2022

Conversation

morepork
Copy link
Contributor

Add a flag to change the requests per second limit when running
istioctl bug-report.

For my test cluster with ~600 pods and the default request limit
of 10, it takes ~5 minutes to collect a bug report. With a 50 rps
limit it takes ~1 minute, and with 100 rps ~35s.

This has become a blocker for collecting bug reports from very
large clusters with thousands of pods.

  • Configuration Infrastructure
  • Docs
  • Installation
  • Networking
  • Performance and Scalability
  • Policies and Telemetry
  • Security
  • Test and Release
  • User Experience
  • Developer Infrastructure

@istio-policy-bot
Copy link

😊 Welcome @morepork! This is either your first contribution to the Istio istio repo, or it's been
awhile since you've been here.

You can learn more about the Istio working groups, code of conduct, and contributing guidelines
by referring to Contributing to Istio.

Thanks for contributing!

Courtesy of your friendly welcome wagon.

@google-cla
Copy link

google-cla bot commented Aug 31, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@istio-testing istio-testing added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-ok-to-test labels Aug 31, 2022
@istio-testing
Copy link
Collaborator

Hi @morepork. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@@ -472,29 +471,6 @@ func appendGlobalErr(err error) {
lock.Unlock()
}

func BuildClientsFromConfig(kubeConfig []byte) (kube.Client, error) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this was unused before my changes

@@ -34,31 +34,50 @@ import (

const (
// maxRequestsPerSecond is the max rate of requests to the API server.
maxRequestsPerSecond = 10
// maxLogFetchConcurrency is the max number of logs to fetch simultaneously.
maxLogFetchConcurrency = 10
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't see a lot of value of keeping both these constants as they're the same, and didn't want to add 2 flags for UX reasons, using the rps limit for log fetch concurrency seems like a reasonable choice

Copy link
Member

@GregHanson GregHanson left a comment

Choose a reason for hiding this comment

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

release note looks good

@ericvn
Copy link
Contributor

ericvn commented Aug 31, 2022

/ok-to-test

@istio-testing istio-testing added ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. and removed needs-ok-to-test labels Aug 31, 2022
@morepork
Copy link
Contributor Author

morepork commented Sep 1, 2022

/retest

@istio-testing istio-testing added the needs-rebase Indicates a PR needs to be rebased before being merged label Sep 15, 2022
@morepork morepork force-pushed the bug-report-rps-limit branch from 93278c8 to 79b2767 Compare September 15, 2022 22:43
@istio-testing istio-testing removed the needs-rebase Indicates a PR needs to be rebased before being merged label Sep 15, 2022
@morepork
Copy link
Contributor Author

friendly ping

@incfly
Copy link

incfly commented Sep 20, 2022

@therealmitchconnors @howardjohn @ericvn @istio/wg-test-and-release-maintainers mind taking a look?

@istio-testing istio-testing merged commit 95b2417 into istio:master Sep 23, 2022
@morepork morepork deleted the bug-report-rps-limit branch September 26, 2022 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/perf and scalability area/user experience ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants