Skip to content

Updated QPS and Burst capacity for k8s client #482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

abheda-crest
Copy link
Collaborator

@abheda-crest abheda-crest commented Nov 8, 2024

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):

          env:
            - name: TARGET_DIR
              value: "/etc/kubernetes/secrets-store-csi-providers"
            - name: K8S_CLIENT_QPS
              value: "20.0"
            - name: K8S_CLIENT_BURST
              value: "50"

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.

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.

2 participants