-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.
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
Docs doesn't tell user differences between workflow Stop and Terminate behaviors #4454
Comments
Feel free to submit a PR |
I logged this bug because as end user, I don't know the difference between stop vs terminate workflow. Are they the same?. If not, what are the expected behaviours. |
They seem to be related to "shutdown strategy".
I'm not clear what happens to running nodes. |
In both cases running nodes are stopped.
|
What about adding these notes to the Cobra helper? I can help with this ticket. https://github.com/argoproj/argo/blob/master/cmd/argo/commands/terminate.go#L16 |
Sure, that would be great. I would also find a place in the docs to add the same information |
…argoproj#4454. Signed-off-by: Amim Knabben <amim.knabben@gmail.com>
Summary
I expect CLI docs to tell end user differences between
argo terminate
andargo stop
intentions and its expected behavior. I found none.Diagnostics
What Kubernetes provider are you using?
AWS
What version of Argo Workflows are you running?
2.16
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: