-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix(executor): Delegate PNS wait to K8SAPI executor. #5307
Conversation
Signed-off-by: Alex Collins <alex_collins@intuit.com>
Signed-off-by: Alex Collins <alex_collins@intuit.com>
} | ||
|
||
OUTER: | ||
for _, containerName := range containerNames { |
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.
Very rarely, containers can successfully complete, but the Kubernetes API does not yet know about it, so kubectl logs
will then fail, resulting in the wait container failing.
I don't see any easy way around this, so this reverts us to how v2.12.
It's a shame to lose this performance boost, but a much worse shame to have unpredictable workflow failures.
Signed-off-by: Alex Collins <alex_collins@intuit.com>
@sarabala1979 bump! |
@@ -58,12 +58,7 @@ func (k *K8sAPIExecutor) GetExitCode(ctx context.Context, containerName string) | |||
// Wait for the container to complete | |||
func (k *K8sAPIExecutor) Wait(ctx context.Context, containerNames, sidecarNames []string) error { |
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.
Don't we terminate Sidecar containers also?
No description provided.