Pass Burst and QPS client params to capi k8s clients 1.26

[kdw174]

What type of PR is this?

/kind bug

What this PR does / why we need it:

• Pulls in kube-client-burst and kube-client-qps flags
• Passes the kubeClientBurst and kubeClientQPS flags to the clusterapi provider k8s clients to allow tuning of client and avoid excessive client-side throttling.

Which issue(s) this PR fixes:

Fixes #6333

Does this PR introduce a user-facing change?

- add `--kube-client-burst` and `--kube-client-qps` to control how many requests CA can do against kubernetes
- kubeClientBurst and kubeClientQPS flags are now passed to the clusterapi provider k8s clients

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Cherry pick of #6416 and #5223

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kdw174
Once this PR has been reviewed and has the lgtm label, please assign x13n for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kdw174]

@enxebre or @feiskyer bump on a review for this. Let me know if there's anything else you need. Thanks

[mwielgus]

What about other CA versions? Should we expect cherrypick also to their branches?

[kdw174]

What about other CA versions? Should we expect cherrypick also to their branches?

@mwielgus I've already had PR's merged for 1.27-1.29. Those are linked to the issue

[x13n]

1.26 is past the support window. Even k8s 1.27 end of life is 2024-06-28, so it will get its last CA patch release in May (see schedule).

/close

[k8s-ci-robot]

@x13n: Closed this PR.

In response to this:

1.26 is past the support window. Even k8s 1.27 end of life is 2024-06-28, so it will get its last CA patch release in May (see schedule).

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.