Open tooptoop4 opened 2 weeks ago
Before this fix it would always go into pending because main container was waiting state even though init container already terminated with non-0 exit
This will only be encountered when using ContainerSet
, right?
Before this fix it would always go into pending because main container was waiting state even though init container already terminated with non-0 exit
This will only be encountered when using
ContainerSet
, right?
no, see the logs/comments in the linked issues
Fixes https://github.com/argoproj/argo-workflows/issues/11354 and https://github.com/argoproj/argo-workflows/issues/10717 and https://github.com/argoproj/argo-workflows/issues/10045
Before this fix it would always go into pending because main container was waiting state (https://github.com/argoproj/argo-workflows/blob/4742e9dd6ab2b797d32cb0953849fdcfe82ea325/workflow/controller/operator.go#L1404) even though init container already terminated with non-0 exit
This supersedes https://github.com/argoproj/argo-workflows/pull/13852
cc @terrytangyuan