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

Improve how errors connecting to api-server are handled #129

Closed
aledbf opened this issue Jan 13, 2017 · 0 comments · Fixed by #143
Closed

Improve how errors connecting to api-server are handled #129

aledbf opened this issue Jan 13, 2017 · 0 comments · Fixed by #143
Labels

Comments

@aledbf
Copy link
Member

aledbf commented Jan 13, 2017

In case of errors like issues with serviceaccounts the current code does not show information in the logs. To see something useful is required to increase the verbose level at least to 3.

We should change this and replicate what the dashboard shows when is not possible to reach the api-server

Using HTTP port: 9090
Creating API server client for https://192.168.3.1:443
Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service accounts configuration) or the --apiserver-host param points to a server that does not exist. Reason: the server has asked for the client to provide credentials
Refer to the troubleshooting guide for more information: https://github.com/kubernetes/dashboard/blob/master/docs/user-guide/troubleshooting.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant