-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
kubernetes-credentials-provider 0.13
We get this exception pretty regularly on our jenkins (like every couple hours it seems). It doesn't seem to cause too many issues other than that the KubernetesCredentialProvider restarts.
WARNING c.c.j.p.k.KubernetesCredentialProvider#onClose: Secrets watch stopped unexpectedly jenkins io.fabric8.kubernetes.client.KubernetesClientException: too old resource version: 45504129 (45535373) jenkins at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$1.onMessage(WatchConnectionManager.java:259) jenkins at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323) jenkins at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219) jenkins at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105) jenkins at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274) jenkins at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214) jenkins at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) jenkins at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) jenkins at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) jenkins at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) jenkins at java.lang.Thread.run(Thread.java:748)
the k8s api server is closing watch connections that are old. we catch this and then reconnect to the API server so things will continue to work.
could possibly look at the exception and see if there is anything specific to this that identifies it as a semi expected exception so we don't dump the whole stack
.