A full clientset is cached per logical cluster

The cluster-aware client cache (staging/src/github.com/kcp-dev/apimachinery/pkg/client/constructor.go) keeps a complete typed clientset per cluster path, and several controllers and admission plugins create one for every workspace. In a heap profile after creating 3,000 empty workspaces, clientCache.Cluster retained ~360 MB (~120 KB per workspace).

Suggestion: pass the cluster path per request instead of caching whole clientsets, or cache only the group clients in use.

pass the cluster path per request instead of caching whole clientsets

i can give this a shot, it's the nicer option but also the diff will be big...
/assign

cache only the group clients in use.

this should be a smaller change but still ends up with more redundant memory per WS.

pass the cluster path per request instead of caching whole clientsets

i can give this a shot, it's the nicer option but also the diff will be big...

the change is indeed quite big, but also there is a problem...rate limiting...sharing the same group clients for all LC can be a real problem in a multi shard setup.

cache only the group clients in use.

this should be a smaller change but still ends up with more redundant memory per WS.

client-go/codegen: cache only the group clients in use per LC #4526

Navigation Menu

Repository navigation

A full clientset is cached per logical cluster #4401

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

A full clientset is cached per logical cluster #4401

Description

Activity

neolit123 commented on Oct 30, 2026

neolit123 commented on Oct 30, 2026

neolit123 commented on Oct 30, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions