Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Specify behavior when a container does not exist. #1055

Closed
vicaire opened this issue Oct 22, 2018 · 1 comment
Closed

Specify behavior when a container does not exist. #1055

vicaire opened this issue Oct 22, 2018 · 1 comment
Labels
type/feature Feature request

Comments

@vicaire
Copy link

vicaire commented Oct 22, 2018

FEATURE REQUEST: Behavior when a container does not exist.

When a container does not exist and is used as a step of the workflow, it seems that Argo retries forever.

Could we make this behavior configurable for each step so that, for instance, we could specify that there should be no retires, retries, or a timeout?
@jessesuen jessesuen added the type/feature Feature request label Jan 22, 2019
icecoffee531 pushed a commit to icecoffee531/argo-workflows that referenced this issue Jan 5, 2022
@whynowy
fix: Use different clientID for each EventBus reconnection. Fixes arg…
bf63a4d 
…oproj#1055 (argoproj#1061)

* fix: Use differet clientID for each EventBus reconnection. Fixes argoproj#1055

Signed-off-by: Derek Wang <whynowy@gmail.com>

* comment

Signed-off-by: Derek Wang <whynowy@gmail.com>

* tiny

Signed-off-by: Derek Wang <whynowy@gmail.com>
@alexec
Copy link
Contributor

alexec commented Feb 7, 2022

I've not need this behaviour. Please re-open if you see it.

@alexec alexec closed this as completed Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature Feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexec @jessesuen @vicaire