Updated QPS and Burst capacity for k8s client #482
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.
The PR focuses on updating QPS and Burst capacity for k8s client to handle a higher frequency of SA token retrieval. These configurations are now set via environment variables in deployment config, providing flexibility for adjusting values as per requirement. Additionally, the load test has been updated to reflect these changes.
Related to: #198 & #383
Example (deploy/provider-gcp-plugin.yaml):
Tested in the GKE environment across various configurations demonstrated successful scaling under moderate loads.
For ~100 secrets, the GKE environment remained stable across all tested pod and node configurations, supporting ~300 pods without issues.