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

Kube API server connection indicator on UI #553

Open
christophenne opened this issue Apr 23, 2024 · 0 comments
Open

Kube API server connection indicator on UI #553

christophenne opened this issue Apr 23, 2024 · 0 comments
Labels

Comments

@christophenne
Copy link
Member

Is your feature request related to a problem? Please describe.
While using the UI, the connection to the API server (especially in the watch loops) could be lost. I had this issue recently when using glasskube in my OVH cluster, and then running a security patch of the kubernetes cluster, where the watch loop seems to have been disturbed at least:

W0423 13:21:29.949641   75118 reflector.go:462] pkg/mod/k8s.io/client-go@v0.29.4/tools/cache/reflector.go:229: watch of *v1alpha1.Package ended with: Internal error occurred: rpc error: code = Unknown desc = context canceled
W0423 13:30:29.677213   75118 reflector.go:462] pkg/mod/k8s.io/client-go@v0.29.4/tools/cache/reflector.go:229: watch of *v1alpha1.Package ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
W0423 13:30:29.677265   75118 reflector.go:462] pkg/mod/k8s.io/client-go@v0.29.4/tools/cache/reflector.go:229: watch of *v1alpha1.PackageInfo ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding

Interestingly, it seems that afterwards the connection has come back up automatically. Either way, we should investigate this (maybe there are also other cases where the watch loop is cancelled / terminated) and find a way to show this information and how to resolve it to the user on the UI, e.g. "It seems that your Kubernets API server is not reachable – please check again and restart with glasskube server".

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant