-
Notifications
You must be signed in to change notification settings - Fork 104
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
Konnectivity unable to recover after crash #632
Comments
This might be a good reason for #598, as that will remove the use of a unix socket. Not sure about other possible workarounds. |
I don't think #598 would solve your issue, mostly because the UDS is required for the API Server and Konnectivity Server interaction. May I ask you which version of Konnectivity Server are you running on? |
For this cluster Konnectivity v0.0.32, due to an older Kubernetes version it seems. |
Until we have enough data to debug, as well as logs, I'm asking if you could try updating You can override the tag by specifying You can browse published container images using this link. |
kubernetes-sigs/apiserver-network-proxy#498 seems solving your issue, if you agree I'd close this bug report since a newer version of Konnectivity will fix your issue. |
For an unknown reason, our Konnectivity crashes from time to time. We have not found the exact reason for the crash, but after that it Konnectivity is unable to recover and thus keeps on crashing.
The error when it keeps on crashing is as follows:
This issue specifically focuses on the fact that Konnectivity is unable to recover after a crash.
The text was updated successfully, but these errors were encountered: