Skip to content

wait container | Failed to establish pod watch ... dial tcp i/o timeout #4980

Answered by terrytangyuan
RysBen asked this question in Q&A
Discussion options

You must be logged in to vote

Copying my response from #4993 to this discussion and hopefully others will find it useful as well:

It's likely that your cluster/apiserver is super unstable. There's an environment variable TRANSIENT_ERROR_PATTERN you can use to specify a regular expression for additional errors that you'd like to retry. There are also variables like RETRY_BACKOFF_* that you can set as well for further customization of the retry behavior. More details in this doc: https://github.com/argoproj/argo-workflows/blob/master/docs/environment-variables.md

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
2 replies
@RysBen
Comment options

@terrytangyuan
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by terrytangyuan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants