kubectl exec fails via kubeapi-load-balancer when StreamingProxyRedirects feature is disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes API Load Balancer |
Fix Released
|
High
|
Kevin W Monroe | ||
Kubernetes Control Plane Charm |
Fix Released
|
High
|
George Kraft |
Bug Description
The StreamingProxyR
When running a `kubectl exec` command, if the connection goes through kubeapi-
error: unable to upgrade connection: unable to upgrade: missing upgrade headers in request: http.Header{
If kubeapi-
The logging around this in kube-apiserver and kubelet, even with v=100, is sparse. Somewhere between kube-apiserver and kubelet, the Connection header changes from "Upgrade" to "close Upgrade", and that is likely killing the connection. It is unclear where the "close" comes from.
It is also unclear how StreamingProxyR
Changed in charm-kubeapi-load-balancer: | |
importance: | Undecided → High |
Changed in charm-kubernetes-master: | |
importance: | Undecided → High |
Changed in charm-kubeapi-load-balancer: | |
status: | New → Triaged |
Changed in charm-kubernetes-master: | |
status: | New → Triaged |
Changed in charm-kubeapi-load-balancer: | |
status: | Invalid → Triaged |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubeapi-load-balancer: | |
milestone: | none → 1.24 |
assignee: | nobody → Kevin W Monroe (kwmonroe) |
status: | Triaged → In Progress |
Changed in charm-kubeapi-load-balancer: | |
status: | Fix Committed → Fix Released |
PR: https:/ /github. com/charmed- kubernetes/ charm-kubernete s-master/ pull/173