You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have randomly an issue with Argo workflows running a java application in a pod on our Kubernetes environments.
The wait container starts successfully after istio-proxy container and before main container.
(we use Istio as service mesh in our Kubernetes environments).
From time to time, JVM of main container only outputs the initial log indicating that it picked up _JAVA_OPTIONS.
The java application shuts down with error code 1 after a few seconds without any additional log:
Picked up _JAVA_OPTIONS: -XX:MaxRAMPercentage=35 -XX:InitialRAMPercentage=25
time="2025-05-14T14:00:34.338Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 1
Checking pod and workflow events did not provide any additional information.
Same for logs of argo-workflows controller.
Has anyone encountered a similar issue ?
I've also attached pod CR and workflow CR to the discussion for more details.
Docker image used in main container contains java17 application and envoy-preflight executable to shut down istio-proxy at the end of the batch.
Any assistance to understand the root cause of this issue would be appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We have randomly an issue with Argo workflows running a java application in a pod on our Kubernetes environments.
The wait container starts successfully after istio-proxy container and before main container.
(we use Istio as service mesh in our Kubernetes environments).
From time to time, JVM of main container only outputs the initial log indicating that it picked up _JAVA_OPTIONS.
The java application shuts down with error code 1 after a few seconds without any additional log:
Checking pod and workflow events did not provide any additional information.
Same for logs of argo-workflows controller.
Has anyone encountered a similar issue ?
I've also attached pod CR and workflow CR to the discussion for more details.
Docker image used in main container contains java17 application and envoy-preflight executable to shut down istio-proxy at the end of the batch.
Any assistance to understand the root cause of this issue would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions