-
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
Fixed kube-proxy birthCry event as it seemed to start too early #13669
Fixed kube-proxy birthCry event as it seemed to start too early #13669
Conversation
had a possibility to not start successfully after the event was already posted.
da88314
to
599100d
Compare
GCE e2e build/test passed for commit da883148748a2b9be11176dbdd054b405ec8fdf6. |
Labelling this PR as size/XS |
GCE e2e build/test failed for commit 599100d. |
@kubernetes/rh-cluster-infra |
LGTM |
1 similar comment
LGTM |
@k8s-bot test this |
GCE e2e build/test passed for commit 599100d. |
GCE e2e build/test passed for commit 599100d. |
The author of this PR is not in the whitelist for merge, can one of the admins add the 'ok-to-merge' label? |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 599100d. |
Automatic merge from SubmitQueue |
Auto commit by PR queue bot
Fixed kube-proxy birthCry event as it seemed to start too early and
had a possibility to not start successfully after the event was already
posted.