x/net/http2: slow streaming with http2 due to MaxConcurrentStreams

[krasi-georgiev]

The k8s go client doesn't behave well since the change in golang/net@1c05540

What happens is that when the client hits the MaxConcurrentStreams of the server any updates after that take very long time (1-2 minutes) so on k8s clusters with constant changes the client can never catch up.
The fix in that commit seems valid, but shouldn't the retry interval can be configurable or provide an option to open a new connection like with the old behaviour.

More on the issue: kubernetes/client-go#456

go version go1.11 linux/amd64

[krasi-georgiev]

cc @tombergan

[krasi-georgiev]

I will try to make a reproducible test, but in the meanwhile some initial input would be useful.

[meirf]

This looks like a dup of #27044 so I'm closing, but tagging @bradfitz to take a look at 27044 due to the urgency that usually comes with k8s issues.