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

Set timeouts for kube client #7

Merged
merged 1 commit into from
Jun 15, 2018
Merged

Set timeouts for kube client #7

merged 1 commit into from
Jun 15, 2018

Conversation

mikkeloscar
Copy link
Owner

Run the kube client with timeouts instead of the default where there's no timeouts at all.

@coveralls
Copy link

Coverage Status

Coverage decreased (-1.04%) to 45.045% when pulling 865d18e on client-go-timeouts into 7c71e02 on master.

@aermakov-zalando
Copy link
Collaborator

👍

@mikkeloscar mikkeloscar merged commit 02f51f6 into master Jun 15, 2018
TLSHandshakeTimeout: 10 * time.Second,
ResponseHeaderTimeout: 10 * time.Second,
ExpectContinueTimeout: 1 * time.Second,
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/zalando/skipper/blob/master/dataclients/kubernetes/kube.go#L299-L326
Looks good to me, but I think you should add the goroutine that closes idle connections in case this transport hast to do another DNS lookup for whatever reason. golang/go#23427

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this specific case it's not really needed since the controller just goes to 10.3.0.1.

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