Konnectivity server is incompatible with go std lib

[steeling]

Go stdlib allows setting a proxy in the http.Transport object. When a proxy is set, and the destination uses HTTPS, it sends a CONNECT pass through request. However if the destination is HTTP, it sends a get request.

curl behaves the same.

This is incongruent with konnectivity which requires all requests to be CONNECT passthrough

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[steeling]

/remove-lifecycle stale

[steeling]

This is made worse by the fact that go reuses connections, so if you were to do some custom stuff to the transport to try to circumvent this restriction, then you run into an issue where you might reuse the wrong conn

https://cs.opensource.google/go/go/+/refs/tags/go1.23.4:src/net/http/transport.go;l=1926

How does the apiserver get around this? I'll try digging through api server code later to find the answer, but if anybody has a link that'd be helpful