Websocket connection issues encountered when using fabric8 kubernetes-client 6.7.2 with IPv6?

[Ranjith4500]

We are attempting to utilize the Kubernetes watch functionality using fabric8 kubernetes-client 6.7.2. While it successfully establishes a websocket connection in IPv4, but the websocket connection is not opening in IPv6.

I have developed a simple standalone client to invoke the Kubernetes watch functionality using fabric8 kubernetes-client 6.7.2. In this implementation, I have excluded the okhttp dependencies provided by fabric8 kubernetes-client and externalized the dependency by upgrading to version 4.9.0. However, I encountered an issue where the client fails to establish websocket connections in an IPv6 setting.

And we have tried using this client https://github.com/rohankanojia-forks/fabric8-okhttp-ipv6-k8s-cluster-bug-reproducer with this, we are get below error

Exception in thread "OkHttp Dispatcher" java.lang.IllegalStateException: Unbalanced enter/exit
at okio.AsyncTimeout.enter(AsyncTimeout.kt:49)
at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:329)
at okio.RealBufferedSource.indexOf(RealBufferedSource.kt:427)
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.kt:320)
at okhttp3.internal.http1.HeadersReader.readLine(HeadersReader.kt:29)
at okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders(Http1ExchangeCodec.kt:178)
at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:106)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:79)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at io.fabric8.kubernetes.client.utils.BackwardsCompatibilityInterceptor.intercept(BackwardsCompatibilityInterceptor.java:133)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at io.fabric8.kubernetes.client.utils.TokenRefreshInterceptor.intercept(TokenRefreshInterceptor.java:42)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at io.fabric8.kubernetes.client.utils.ImpersonatorInterceptor.intercept(ImpersonatorInterceptor.java:68)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at io.fabric8.kubernetes.client.utils.HttpClientUtils.lambda$createApplicableInterceptors$6(HttpClientUtils.java:290)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

[shawkins]

Would it be possible to try one of the other http clients instead?

[Ranjith4500]

I tried using the Jetty and Vertex clients, unfortunately the web sockets are not opening for both.
In case of jetty getting seeing below logs

Evict skipped, no excess threads QueuedThreadPool[WebSocket@1644236636]@327bcebd{STARTED,8<=8<=200,i=6,r=-1,t=58594ms,q=0}[ReservedThreadExecutor@1d7f7be7{reserved=1/1,pending=0}]

On the other hand, with Vertex, the thread appears to get stuck during the handshake.

[shawkins]

So no stacktrace from any of the clients with 6.7.2? If none of the clients work, I'd wonder if we're hitting any api-server issue. Are you able to see if what your trying to do can be done successfully with a go client? Something like kubernetes/kubernetes#102464 (comment)