Skip to content
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

Increase the time we wait for the kubelet to be healthy. #6304

Merged
merged 1 commit into from
Apr 2, 2015

Conversation

roberthbailey
Copy link
Contributor

I've seen a few shippable failures this morning (e.g. https://app.shippable.com/builds/551c40a8f019730b00b3b15a) where it looks like the kubelet isn't responding healthy before the default 2 second timeout is reached. Increase the timeout to 5 seconds to give the kubelet more time to initialize.

@vmarmol
Copy link
Contributor

vmarmol commented Apr 1, 2015

LGTM, but needs a rebase.

@vmarmol vmarmol self-assigned this Apr 1, 2015
@yujuhong
Copy link
Contributor

yujuhong commented Apr 1, 2015

The overall performance on Shippable somehow got worse recently. We had to increase the timeout for many things, and the list keeps growing :\

@vmarmol
Copy link
Contributor

vmarmol commented Apr 1, 2015

It's also incredibly flaky lately as well...

@roberthbailey
Copy link
Contributor Author

Rebased.

@vmarmol
Copy link
Contributor

vmarmol commented Apr 1, 2015

Thanks! Will merge on green.

vmarmol added a commit that referenced this pull request Apr 2, 2015
Increase the time we wait for the kubelet to be healthy.
@vmarmol vmarmol merged commit 312bc71 into kubernetes:master Apr 2, 2015
@roberthbailey roberthbailey deleted the test-cmd-timeout branch April 9, 2015 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants