Add Kubernetes client QPS and Burst configuration support. #998
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.
In clusters with many VaultStaticSecrets, the default Kubernetes client QPS of 5 and Burst of 10 is insufficient, leading it to throttle its communications with the Kubernetes API. This can cause brand-new deployments to roll out very slowly as their pods wait for their Kubernetes secrets to be created from their VaultStaticSecrets.
This change exposes the operator's Kubernetes client QPS and Burst configuration via cli arguments and environment variables, as well as explicitly via chart values.
--kube-client-qps
and--kube-client-burst
cli argsVSO_KUBE_CLIENT_QPS
andVSO_KUBE_CLIENT_BURST
env var support.Values.controller.manager.kubeClient.qps
and.burst
to chart.Values.controller.manager.extraEnv
values