Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Kubernetes Configuration Watcher failed to connect and stopped watching for changes
See original GitHub issueWe are using watcher pod to watch on secret/configmap changes. From time to time it raises connection errors and watcher pod stopped watch for changes, it didn’t try even to reconnect.
samples errors :
- Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210)
- java.net.ConnectException: Failed to connect to /***:443 at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:265) *java.io.EOFException: null at okio.RealBufferedSource.require(RealBufferedSource.java:65)
And always we see WatchConnectionManager : Exec Failure
Currently I monitor errors in the watcher and restart the watcher when received errors, but we must get a normal solution. Any idea how can it be fixed? or even workaround? code changes? can I catch this errors and trigger a reconnect?
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As far as I can see you are moving away from fabric8 client so I am going to deploy the watcher with kubernetes official client and see if issue is gone. (And I could not reproduce the issue locally 😄)
Once you have a reliable way of reproducing the problem let me know and I will take a look