Adapt CCM Azure API's client rate limits based on cluster size
kon-angelo opened this issue · comments
How to categorize this issue?
/area control-plane
/kind bug
/platform azure
What happened:
Currently we set the QPS for Azure API operations based on the maximum number of nodes in the cluster (ref) but the Buckets are set statically. For very large clusters where QPS>>bucket we see that we hit easily the rate limits for certain operations (particularly NicGet operations that are not cached). For these cases the Buckets function as a limiter of available operations rather than providing Burst capacity.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- Gardener version (if relevant):
- Extension version:
- Kubernetes version (use
kubectl version): - Cloud provider or hardware configuration:
- Others: