Skip to content

feat: setting a higher default max conccurent request for client #1637

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

Merged
merged 2 commits into from
Dec 1, 2022

Conversation

csviri
Copy link
Collaborator

@csviri csviri commented Nov 30, 2022

No description provided.

@csviri csviri self-assigned this Nov 30, 2022
@csviri csviri linked an issue Nov 30, 2022 that may be closed by this pull request
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@csviri csviri merged commit 1ec4d7c into main Dec 1, 2022
@csviri csviri deleted the max-concurrent-request branch December 1, 2022 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use greater default value for Kubernetes Client max request value
2 participants