Executing command in pod fails when _request_timeout is passed in tuple format #2292
Comments
|
/assign @yliaog |
|
timeout should be a float, not a tuple as the error suggests Exception when calling CoreV1Api->connect_get_namespaced_pod_exec: (0) Reason: '<' not supported between instances of 'float' and 'tuple' |
|
Hi @yliaog, Thanks for looking into this. The documentation for the API mentions If there is another way to set connect_timeout, let me know. Thanks again ! |
|
I see. please checkout https://github.com/kubernetes-client/python/blob/master/examples/watch/timeout-settings.md |
|
In case if the pod is on a node which is network partitioned and if you execute command in a pod running on that node, it will take 30 seconds to timeout even if you set "_request_timeout" to be a lesser value. If you use curl with "connect_timeout" to a smaller value, it does timeout after that duration so we need to set connect_timeout for the "connect_get_namespaced_pod_exec" api so that it can timeout during network partition. The only option I see in kubernetes client is to set the _request_timeout to a tuple value which allows to set "connect_timeout" which is not working. Can you please check if there is an issue ? |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
/remove-lifecycle stale |
|
python/kubernetes/base/stream/ws_client.py Line 225 in e104702 I think the error was caused by the above line, where timeout was only allowed to be a float, not a tuple. |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
|
Same problem as explained in #2292 (comment) and #2292 (comment). I haven't found any good enough workaround. One extra detail: if you set |
|
As mentioned in #2292 (comment), I think we need some parsing like here when handling the timeout here /help
Does setting |
|
@roycaihw: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
What happened (please include outputs or screenshots):
Executing command in pod fails if _request_timeout is passed as tuple.
The exact error is
Exception when calling CoreV1Api->connect_get_namespaced_pod_exec: (0) Reason: '<' not supported between instances of 'float' and 'tuple'What you expected to happen:
Expected to run the command successfully.
How to reproduce it (as minimally and precisely as possible):
`from kubernetes import client, config
from kubernetes.stream import stream
def run_command_in_pod(namespace, pod_name, container_name, command, timeout):
config.load_kube_config()
c = client.Configuration()
c.debug = True
api_instance = client.CoreV1Api()
if name == 'main':
namespace = 'test'
pod_name = 'test'
container_name = 'test'
command = 'date'
timeout = (5, 10)
Anything else we need to know?:
Environment:
kubectl version): 1.30python --version) 3.9pip list | grep kubernetes) kubernetes-31.0.0The text was updated successfully, but these errors were encountered: