Cluster-api: Set User Agent and Request Timeout for Remote Cluster Caches

[JoelSpeed]

User Story

We should set a user agent on the clients used by the remote cluster caches introduced in #2880 so that request logs can be tracked back to the cluster caches.

We should also set a Timeout on the requests so that failed connections time out rather than hanging

(Originally suggested by @fabriziopandini and @ncdc)

/kind feature

[vincepri]

/milestone v0.3.x
/help
/priority important-longterm

[k8s-ci-robot]

@vincepri:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/milestone v0.3.x
/help
/priority important-longterm

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/test-infra repository.

[spagno]

/assign
/lifecycle active

[vincepri]

/milestone v0.4.0

[evalsocket]

/assign @evalsocket

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fabriziopandini]

/remove-lifecycle stale

[detiber]

/lifecycle frozen

[vincepri]

/assign @nader-ziada

[nader-ziada]

/lifecycle active

[nader-ziada]

I think I need a little bit more context, can't find any previous conversations about this, is it just adding the user agent and timeout to the remote cluster client?

[fabriziopandini]

Yes, it is just that.
The user agent can be helpful when auditing API server calls
The timeout helps to avoid being blocked (by default the client waits forever)