Saravanan Balasubramanian

@gandeevan I would recommend looking at the load on k8s api server (k8s master). Looks like API request is getting timed out or returning a stream error. Argo will directly...

@gandeevan yes you're right. Can you create an issue on `client-go`? Error is happening on client-go. Argo controller is using the client-go library for informers. ```log "pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: Failed to watch...

@gandeevan you can scale up API server for workaround

@gandeevan great. Would you like to fix this issue and submit the PR?

we won't support v2.12 . Can you upgrade to v3.2 and try it? you right. offloadworkflow is deleted

@tooptoop4 you can't reference the Artifacts content in when condition. The workflow controller doesn't have permission to access the artifact content. There is a workaround you can add one more...

@alexec Are you going to fix it?

@alexec will this code fix this issue? https://github.com/argoproj/argo-workflows/blob/0b2fe2face955f31941496c1a99c13e1b12909d9/workflow/controller/operator.go#L1188-L1192

I am not able to reproduce this issue on my local. controller | ******* Running controller | ***** checking cleanupPod dag-test2-a-4233667491 controller | ***** main &ContainerStateTerminated{ExitCode:137,Signal:0,Reason:OOMKilled,Message:,StartedAt:2022-06-30 16:28:16 -0700 PDT,FinishedAt:2022-06-30 16:28:17...

@tianshimoyi are you seeing `cleaning up pod` in your log once main container exits.