Python: "Upgrade request required" when posting port forward

[yanivoliver]

When attempting to post a port forward to a pod, for example:

v1 = client.CoreV1Api()
v1.connect_post_namespaced_pod_portforward("pod-name", "namespace-name")

An error is thrown:

*** ApiException: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Date': 'Thu, 26 Jul 2018 14:11:26 GMT', 'Content-Length': '139', 'Content-Type': 'application/json'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Upgrade request required","reason":"BadRequest","code":400}

This happens regardless of whether the additional param of 'ports' is passed to the API call.

Environment:

Python 2.7.10 (default, Jul 15 2017, 17:16:57)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.31)] on darwin
Package version: kubernetes (6.0.0)

[slindner05]

Anyone ever make progress on this or get port-forward to work from within the python client?

[ssharma555]

I am facing this issue. Any steps to get this working?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[yanivoliver]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[gpkc]

/remove-lifecycle stale

[micw523]

This should be tracked to #166
/close

[k8s-ci-robot]

@micw523: Closing this issue.

In response to this:

This should be tracked to #166
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.