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

k8s: Back-off retrying to connect to Kubernetes API #1009

Closed
errordeveloper opened this issue Feb 23, 2016 · 0 comments · Fixed by #2562
Closed

k8s: Back-off retrying to connect to Kubernetes API #1009

errordeveloper opened this issue Feb 23, 2016 · 0 comments · Fixed by #2562
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it k8s Pertains to integration with Kubernetes

Comments

@errordeveloper
Copy link
Contributor

Right now the kube probe tries to connect two times, then waits for 10s and tries again. I think we should back-off a bit.

@errordeveloper errordeveloper added the bug Broken end user or developer functionality; not working as the developers intended it label Feb 23, 2016
@errordeveloper errordeveloper changed the title [k8s] back-off retrying to connect to Kubernetes API k8s: back-off retrying to connect to Kubernetes API Feb 25, 2016
@errordeveloper errordeveloper changed the title k8s: back-off retrying to connect to Kubernetes API k8s: Back-off retrying to connect to Kubernetes API Feb 25, 2016
@tomwilkie tomwilkie added the k8s Pertains to integration with Kubernetes label Apr 11, 2016
@rndstr rndstr self-assigned this Jun 1, 2017
rndstr added a commit that referenced this issue Jun 5, 2017
rndstr added a commit that referenced this issue Jun 5, 2017
rndstr added a commit that referenced this issue Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it k8s Pertains to integration with Kubernetes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants