Repository navigation
feat: Allow setting QPS and burst for managed cluster rest configs - #714
Merged
gianlucam76 merged 1 commit intoNov 1, 2026
Merged
Conversation
Clients for managed clusters were created with client-go defaults (5 QPS, burst 10), regardless of what the caller configured for the management cluster. Add clusterproxy.SetRestConfigLimits so a component can set QPS and burst once at startup. The values are applied to every rest.Config returned for a managed cluster (CAPI, Sveltos, admin kubeconfig and workload identity). When the setter is not called, behavior is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clients for managed clusters were created with client-go defaults (5 QPS, burst 10), regardless of what the caller configured for the management cluster. Add clusterproxy.SetRestConfigLimits so a component can set QPS and burst once at startup. The values are applied to every rest.Config returned for a managed cluster (CAPI, Sveltos, admin kubeconfig and workload identity). When the setter is not called, behavior is unchanged.