Skip to content

feat: Separate rate limits for management and managed clusters - #2083

Merged
gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:managed-cluster-rest-limits
Nov 1, 2026
Merged

gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:managed-cluster-rest-limits

Conversation

@gianlucam76

Copy link
Copy Markdown
Member

--kube-api-qps and --kube-api-burst now default to 40 and 120 and apply only to the client for the management cluster. Add --managed-cluster-kube-api-qps and --managed-cluster-kube-api-burst (default 20 and 60) for the clients to managed clusters, passed to libsveltos with clusterproxy.SetRestConfigLimits. Managed cluster clients were limited by the client-go defaults (5 QPS, burst 10).

Requires a libsveltos release containing SetRestConfigLimits.

--kube-api-qps and --kube-api-burst now default to 40 and 120 and apply
only to the client for the management cluster. Add
--managed-cluster-kube-api-qps and --managed-cluster-kube-api-burst
(default 20 and 60) for the clients to managed clusters, passed to
libsveltos with clusterproxy.SetRestConfigLimits. Managed cluster clients
were limited by the client-go defaults (5 QPS, burst 10).

Requires a libsveltos release containing SetRestConfigLimits.
@gianlucam76
gianlucam76 merged commit 28310ee into projectsveltos:main Nov 1, 2026
12 checks passed
@gianlucam76
gianlucam76 deleted the managed-cluster-rest-limits branch November 1, 2026 14:41
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.

1 participant