make connection retry configurable via client configuration

[zq-david-wang]

If a cluster is down, the client would make a default 3 retry for each api call, which sometimes is unnecessary. Adding a field to client configuration indicating how many retries should be used would help deal with this situation.

I used following code and it works

`diff --git a/kubernetes/client/rest.py b/kubernetes/client/rest.py
index 4cdc83bb..173af930 100644
--- a/kubernetes/client/rest.py
+++ b/kubernetes/client/rest.py
@@ -79,6 +79,8 @@ class RESTClientObject(object):
         addition_pool_args = {}
         if configuration.assert_hostname is not None:
             addition_pool_args['assert_hostname'] = configuration.assert_hostname
+        if hasattr(configuration, "retries") and configuration.retries is not None:
+            addition_pool_args['retries'] = configuration.retries
 

[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

[eddieparker]

/remove-lifecycle stale

This would be a nice feature to have - having a higher retry value in certain critical situations would be nice.

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[roycaihw]

fixed in #780

/close

[k8s-ci-robot]

@roycaihw: Closing this issue.

In response to this:

fixed in #780

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