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

[feature request]modify yurt-manager client's default qps and burst #1822

Closed
rambohe-ch opened this issue Nov 23, 2023 · 1 comment · Fixed by #1825
Closed

[feature request]modify yurt-manager client's default qps and burst #1822

rambohe-ch opened this issue Nov 23, 2023 · 1 comment · Fixed by #1825
Assignees
Labels
help wanted help wanted kind/feature kind/feature kind/good-first-issue kind/good-first-issue

Comments

@rambohe-ch
Copy link
Member

What would you like to be added:
The default qps and burst of kube-client in yurt-manager component are defined as follwoing:

RestConfigQPS: 30,
RestConfigBurst: 50,

because more and more controllers are added into yurt-manager, and these values is not enough for yurt-manager to access kube-apiserver, so it is a good idea to up these initial values as followin:

 RestConfigQPS:    50, 
 RestConfigBurst:  100, 

others
/kind feature

@rambohe-ch rambohe-ch added the kind/feature kind/feature label Nov 23, 2023
@rambohe-ch rambohe-ch added help wanted help wanted kind/good-first-issue kind/good-first-issue labels Nov 23, 2023
@lilongfeng0902
Copy link
Member

/assign @lilongfeng0902

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted help wanted kind/feature kind/feature kind/good-first-issue kind/good-first-issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants