You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user sets a timeout, we should ensure that the configured timeout will be roughly respected.
We say roughly because there can be some significant latency for starting a container (on Fargate, even in a range of minutes), so ideally the timeout should start once the container starts. However, the main use case is matching kestra timeout with Cloud container service timeout (even if not 100% accurate) to avoid unexpected costs caused by not respecting timeout and having a zombie container running for weeks.
Feature description
When a user sets a timeout, we should ensure that the configured timeout will be roughly respected.
We say roughly because there can be some significant latency for starting a container (on Fargate, even in a range of minutes), so ideally the timeout should start once the container starts. However, the main use case is matching kestra timeout with Cloud container service timeout (even if not 100% accurate) to avoid unexpected costs caused by not respecting timeout and having a zombie container running for weeks.
The text was updated successfully, but these errors were encountered: