-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multiple containers in worker pod in case for ErrPodCompleted #717
Conversation
In the first place, in the current upstream implementation, exit codes of all containers including
The validation for the exit code for |
f12b598
to
0ba77d2
Compare
@shanemcd |
I like the approach, |
@AaronH88 |
if len(kw.pod.Status.ContainerStatuses) != 1 { | ||
return fmt.Errorf("expected 1 container in pod but there were %d", len(kw.pod.Status.ContainerStatuses)) | ||
} | ||
for _, cstat := range kw.pod.Status.ContainerStatuses { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would love to see this change integrated, as it fixes another problem as well: Running in a cluster with sidecar injection (e.g. istio) enabled. In such a case the 1-container check constantly fails.
0ba77d2
to
09e41b3
Compare
PR #718 added required tests for this, happy to merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Closes #710
Simply, this PR makes Receptor to find
worker
container and invoke the same validation as implemented before in the case forErrPodCompleted
.Passed the same tests as described in #710.
In addition to above, the patterns that container exited with non-zero exit code are also tested;