-
Notifications
You must be signed in to change notification settings - Fork 40k
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
add readiness probe to proxy test #21730
Conversation
Labelling this PR as size/M |
GCE e2e build/test failed for commit 9d87b47. |
Image: config.Image, | ||
Command: config.Command, | ||
Ports: []api.ContainerPort{{ContainerPort: 80}}, | ||
ReadinessProbe: config.ReadinessProbe, |
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 actually need to poll till Ready? Assuming if this method didn't know about readiness before it only polled till Running, but I haven't checked.
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.
One might think so, but it actually already has separate runningButNotReady and runningAndReady states that it prints out in the logs.
The e2e failure is #21769, in case you need a rerun without uploading a new commit |
Handing over to @bprashanth to review; hand back if you'd rather not. |
@k8s-bot test this flake #21769 (thx @bprashanth) |
GCE e2e test build/test passed for commit 9d87b47. |
GCE e2e test build/test passed for commit 9d87b47. |
@k8s-oncall this is a flake fix, please manually merge |
1 similar comment
@k8s-oncall this is a flake fix, please manually merge |
add readiness probe to proxy test
Fixes #21484