Add doc for longer timeout #558
Conversation
openshift-ci
bot
added
the
approved
|
/hold for comments |
openshift-ci
bot
added
the
do-not-merge/hold
|
/lgtm |
liangxia
force-pushed
the
timeout
branch
2 times, most recently
from
c29a15b to
94140f1
Compare
| The `pod.spec.activeDeadlineSeconds` setting on a `Pod` only implicitly bounds the amount of time that a `Pod` executes for on a Kubernetes cluster. The active deadline begins at the first moment that a `kubelet` acknowledges the `Pod`, which is after it is scheduled to a specific node but before it pulls images, sets up a container sandbox, _etc_. It is therefore possible to exceed the active deadline without ever having a container in the `Pod` execute. Please see the [API documentation](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#podspec-v1-core) for more details. For these reasons, no timeout configured in the system makes use of this setting, instead relying on a thin wrapper around the executing code that's injected by Prow itself. | ||
| {{< /alert >}} | ||
|
|
||
| #### How to configure a customize timeout |
There was a problem hiding this comment.
| #### How to configure a customize timeout | |
| #### How to configure a customized timeout |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hector-vido, liangxia, psalajova The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@liangxia: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/unhold |
openshift-ci
bot
removed
the
do-not-merge/hold
3 participants
No description provided.