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
Problem to solve
Let the user adjust this KubeDownscaler timeout (inherited from PyKube library) using an argument
Proposal
Parametrize, inside scaler.py, the pykube constant pykube.http.DEFAULT_HTTP_TIMEOUT to a value that can be choosen by the user using an argument inside KubeDownscaler deployment
Issue
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
Problem to solve
Let the user adjust this KubeDownscaler timeout (inherited from PyKube library) using an argument
Proposal
Parametrize, inside
scaler.py
, the pykube constantpykube.http.DEFAULT_HTTP_TIMEOUT
to a value that can be choosen by the user using an argument inside KubeDownscaler deployment