Large Kubernetes clusters can experience significant client-side throttling during topology reconciliation.
The Kubernetes engine currently performs a per-node GET followed by a full Node update. With client-go defaults of 5 QPS and burst 10, reconciling thousands of nodes can take several minutes.
Kubernetes client rate limits are also configured independently across the DRA provider and Kubernetes-backed engines, requiring duplicated Helm values. The NFD engine does not currently accept these settings and constructs typed and dynamic clients with separate rate limiters.
Large Kubernetes clusters can experience significant client-side throttling during topology reconciliation.
The Kubernetes engine currently performs a per-node GET followed by a full Node update. With client-go defaults of 5 QPS and burst 10, reconciling thousands of nodes can take several minutes.
Kubernetes client rate limits are also configured independently across the DRA provider and Kubernetes-backed engines, requiring duplicated Helm values. The NFD engine does not currently accept these settings and constructs typed and dynamic clients with separate rate limiters.