Workflow workers and TTL worker are silently stoped if any handled panic in processingNextItem function #5367
Assignees
Labels
Comments
mweibel
added a commit
to mweibel/argo
that referenced
this issue
May 4, 2021
allows to specify windows OS version using `--build-arg IMAGE_OS_VERSION=1909` so users can build their own argoexec using the appropriate underlying windows version (see argoproj#5367). Signed-off-by: Michael Weibel <[email protected]>
mweibel
added a commit
to mweibel/argo
that referenced
this issue
May 7, 2021
allows to specify windows OS version using `--build-arg IMAGE_OS_VERSION=1909` so users can build their own argoexec using the appropriate underlying windows version (see argoproj#5367). Signed-off-by: Michael Weibel <[email protected]>
alexec
pushed a commit
that referenced
this issue
May 7, 2021
allows to specify windows OS version using `--build-arg IMAGE_OS_VERSION=1909` so users can build their own argoexec using the appropriate underlying windows version (see #5367). Signed-off-by: Michael Weibel <[email protected]>
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
What happened/what you expected to happen?
Diagnostics
What Kubernetes provider are you using?
What version of Argo Workflows are you running?
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: