fix stream bug when use ssl

[Novelfor]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Stream api will block data when use ssl socket.

Which issue(s) this PR fixes:

Fixes #2414

Special notes for your reviewer:

According to this document https://docs.python.org/3/library/ssl.html#ssl-nonblocking, select() may lose some data, it only happen when use ssl socket

I test the code in my self-host kubernetes server

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Novelfor
Once this PR has been reviewed and has the lgtm label, please assign roycaihw for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• kubernetes/base/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

• ✅login: Novelfor / (764cc34)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @Novelfor!

It looks like this is your first PR to kubernetes-client/python 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/python has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[ivaradi]

I think this could be improved by calling poll/select only when ssl_pending is 0.

[roycaihw]

/assign

[roycaihw]

Could you add a test?

[Novelfor]

Current e2e test has stream exec test. but i think it's not easy to find ssl blocking by current test code.

1. The blocking is not clearly observable in the program (if the data is sent continuously, once the next chunk is sent, it will also carry over any previously blocked data).
2. Setting up SSL in minikube requires additional work.
   I can think about designing a reliable testing approach later, it's not easy to write a work test (current e2e case https://github.com/kubernetes-client/python/blob/master/kubernetes/e2e_test/test_client.py#L130 contain stream exec test, but it hard to reflect blocking). But I hope we can merge this first so that I don't have to keep using my own forked version on my cluster.