See this once in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/124467/pull-kubernetes-e2e-kind-ipv6/1782694702064078848 but the error does not look right

> { failed [FAILED] Container port output missing expected value. Wanted:'It works!', got: Client sent an HTTP request to an HTTPS server.
> In [It] at: k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:554 @ 04/23/24 09:14:34.283
> }

how can port forward send this to an https server?

```
STEP: forwarding the container port to a local port - k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:542 @ 04/23/24 09:14:34.071
I0423 09:14:34.071990 69210 portforward.go:180] starting port-forward command and streaming output
I0423 09:14:34.072086 69210 util.go:585] Asynchronously running '/home/prow/go/src/k8s.io/kubernetes/_output/bin/kubectl kubectl --server=https://[::1]:34783 --kubeconfig=/root/.kube/kind-test-config --namespace=kubectl-6707 port-forward --namespace=kubectl-6707 httpd :80'
I0423 09:14:34.072534 69210 portforward.go:189] reading from `kubectl port-forward` command's stdout
STEP: curling local port output - k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:546 @ 04/23/24 09:14:34.276
I0423 09:14:34.277776 69210 kubectl.go:549] got: Client sent an HTTP request to an HTTPS server.

[FAILED] Container port output missing expected value. Wanted:'It works!', got: Client sent an HTTP request to an HTTPS server.
```

are we. leaking connections or not redirecting it correctly and the upgreadware proxy fails?

/cc @liggitt @seans3 

/kind flake
[Flake]  [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : [Flake]  [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward
Issue date:

--- start body ---
See this once in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/124467/pull-kubernetes-e2e-kind-ipv6/1782694702064078848 but the error does not look right

> { failed [FAILED] Container port output missing expected value. Wanted:'It works!', got: Client sent an HTTP request to an HTTPS server.
> In [It] at: k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:554 @ 04/23/24 09:14:34.283
> }

how can port forward send this to an https server?

```
STEP: forwarding the container port to a local port - k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:542 @ 04/23/24 09:14:34.071
I0423 09:14:34.071990 69210 portforward.go:180] starting port-forward command and streaming output
I0423 09:14:34.072086 69210 util.go:585] Asynchronously running '/home/prow/go/src/k8s.io/kubernetes/_output/bin/kubectl kubectl --server=https://[::1]:34783 --kubeconfig=/root/.kube/kind-test-config --namespace=kubectl-6707 port-forward --namespace=kubectl-6707 httpd :80'
I0423 09:14:34.072534 69210 portforward.go:189] reading from `kubectl port-forward` command's stdout
STEP: curling local port output - k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:546 @ 04/23/24 09:14:34.276
I0423 09:14:34.277776 69210 kubectl.go:549] got: Client sent an HTTP request to an HTTPS server.

[FAILED] Container port output missing expected value. Wanted:'It works!', got: Client sent an HTTP request to an HTTPS server.
```

are we. leaking connections or not redirecting it correctly and the upgreadware proxy fails?

/cc @liggitt @seans3 

/kind flake
--- end body ---

None