Skip to content
This repository has been archived by the owner on Apr 19, 2021. It is now read-only.

Handle issues when connecting to kubernetes properly #12

Open
ankon opened this issue Dec 11, 2017 · 1 comment
Open

Handle issues when connecting to kubernetes properly #12

ankon opened this issue Dec 11, 2017 · 1 comment

Comments

@ankon
Copy link
Contributor

ankon commented Dec 11, 2017 

(node:16) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 44): Error: connect ECONNREFUSED 10.3.0.1:443

This can happen when there are problems reaching the API server. Right now the service continues to run, but will not actually do anything anymore. We should either apply some retrying logic here, or just outright crash and rely on kubernetes to restart the pod.
@ankon
Copy link
Contributor Author

ankon commented Jan 30, 2018

This appeared again in our production setup. If making the service crash is too hard then at least having some form of "live-ness" check would be needed, so that the system-as-a-whole can react.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ankon