New Feature: Introduced An Argument To Customize Timeout When Contacting API Server #106
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.
Motivation
In some circumstances that I still wasn't able to replicate, KubeDownscaler will timeout when processing a resources. This is most probably caused by a slow communication between the Pod and the Kubernetes API Server. This may happen because a network bottleneck or because the API Server itself is busy processing other requests
Changes
scaler.py
, the pykube constantpykube.http.DEFAULT_HTTP_TIMEOUT
, is set to a value that can be choosen by the user using an argument inside KubeDownscaler deployment. If the user doesn't set a value, the default is 10 (as in the previous versions)Tests done
TODO