Steven Hawkins

My initial take is that support for this in the various clients is problematic. [This](https://bugs.openjdk.org/browse/JDK-8294170) seems to suggest it's not supported by JDK and I only see implicit support for...

> I also can't find any such code in the kubectl source although kubectl seems to work fine with that. The handling should be further down in client-go, then in...

> This did not work: Thinking more about it this wouldn't influence the handshake unless that was somehow already baked into the proxy handling of each client. > But the...

> However, I'm puzzled as to what is the real problem or bug that creates this behavior. If kubectl works with a given KUBECONFIG then I expect the java clients...

> If I wanted to try with jetty, how would I configure the fabric8 kubernetes client to use jetty http client? You can try it by adding the jetty httpclient...

@winitzki it means code changes are needed - nothing is passing that down to the http client layer currently, then the handling for it would need to be added to...

Should be the same issue as #4503 - some other unshown dependency is bring in a conflicting version of the fabric8 kubernetes client. That issue and the faq have been...

Removed the never stale to see if we can move this towards a resolution. It's not clear to me yet what belongs down in the fabric8 client for this. One...

> But, might be interesting to put it into fabric8 directly. I can also see that it would be pretty straight-forward to have event handler that omits locally generated events,...

Marking as closed. There is too much refactoring to make this happen any time soon.