binary websocket support, plus examples

[aogier]

Hello, in #476 we noted that we currently cannot stream binary data to/from pods so no feature like kubectl cp (and probably others) could be implemented.

I've worked on that, two PR came out. The first is kubernetes-client/python-base#52 and when it will be merged, this one will then unlock binary streams and provide couple examples on how to do it.

Problem: I had to patch core_v1_api.py swagger generated code, as swagger itself seems to ignore binary type specification. I'm currently investigating on that.
In the meanwhile I could produce a temporary patch in scripts/ and apply it when client-updateing but I'd like to know what do you think about that part.

Thank you, ciao

[aogier]

I think I've successfully patched swagger in swagger-api/swagger-codegen@676da33 although my tests aren't supported by a successful CI run because starting branch obsolescence.

Basically I'm using six.binary_type that translate to str on py2 (no-op), and bytes on py3 and this need to be checked throughly against py3 tests in python-base (afaict python-client tests are empty, and for sure they return OK).

I'll work on testing against our needs but seems promising !

[fejta-bot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/check-cla

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.