Menu
How can I set the timeout for the kubectl exec command ?
The below command does not work
kubectl exec -it pod_name bash --requrest-timeout=0 -n test
499
To limit the ability to kubectl exec to pods what you want to do is create a custom Role & RoleBinding that removes the create verb for the pods/exec resource. An easy approach to this might be to copy the default RBAC policies, and then make the appropriate edit and rename.
The kubectl exec command lets you start a shell session inside containers running in your Kubernetes cluster. This command lets you inspect the container's file system, check the state of the environment, and perform advanced debugging tools when logs alone don't provide enough information.
Unfortunately, there is no way to make it faster. A lot of actions are supposed to be done by Kubernetes to restart pods from a failed node. However, it is possible to enhance reaction time. For example, reduce the value of node-monitor-grace-period, default is 40 seconds.
Rationale: Setting idle timeouts ensures that you are protected against Denial-of-Service attacks, inactive connections and running out of ephemeral ports. Note: By default, --streaming-connection-idle-timeout is set to 4 hours which might be too high for your environment.
You have a typo, try:
kubectl exec -it pod_name bash --request-timeout=0 -n test
See kubectl official documentation about request-timeout
--request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
Note that "0" is already the default.
169
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
