-
Notifications
You must be signed in to change notification settings - Fork 6
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
Annoying "http: TLS handshake error" in logs #104
Comments
It would be nice to get to the bottom of this annoying bug. I still see this spamming the logs after upgrading to the latest version of Accurate (1.3.0):
Am I the only one observing this? 🤔 @yamatcha, what about your installations of Accurate? |
@erikgb |
No, not at present. Waiting for our network expert to become available. But we don't see this problem in any other operator installed in our cluster. And we have quite a few.... |
@erikgb |
same error
|
What
We are òbserving some mysterious errors in the Accurate pods:
Are anyone else observing something similar? The operator seems to work as it should, so this is just annoying messages in the logs. I suspect this might be related to kubernetes/kubernetes#109022, and some suspect the root issue to be golang/go#50984.
I'll suggest addressing #103 to see if that can fix this issue.
How
Describe how to address the issue.
Checklist
The text was updated successfully, but these errors were encountered: