Proxy sidecar exits with non-zero exit code on SIGTERM #5044
Unanswered
agniveshadhikari
asked this question in
Q&A
Replies: 2 comments
-
@cpretzer you've messed around with Argo most recently, any ideas? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I didn't get far enough with Argo to see anything like this. It looks like the proxy is starting up and shutting down very quickly, so I'd start by looking at when and why Argo is sending that SIGTERM. I wonder if the proxy has not fully started when it receives the SIGTERM command. I'd also set the trace proxy-log-level just to see if there's more detail about what the proxy is doing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to use Linkerd within an argo workflow. I am aware of the issues that are to be expected when trying to use sidecars with jobs.
Argo somehow seems to send a SIGTERM to the linkerd sidecar, but it exits with non-zero exit code. I believe it should have exited with 0 code, and that could have made my workflow succeed. Can you help me understand what is going on here a little better?
As you can see here, the argo workflow fails:

Here is the message (from the above image. Copy-pasted here for better readability)
Here is a part of the describe on the pod:
Beta Was this translation helpful? Give feedback.
All reactions