Mike Spreitzer 201c11f147 Fixes for HTTP/2 max streams per connection setting ... This PR makes two changes. One is to introduce a parameter for the HTTP/2 setting that an api-server sends to its clients telling them how many streams they may have concurrently open in an HTTP/2 connection. If left at its default value of zero, this means to use the default in golang's HTTP/2 code (which is currently 250). The other change is to make the recommended options for an aggregated api-server set this limit to 1000. The limit of 250 is annoyingly low for the use case of many controllers watching objects of Kinds served by an aggregated api-server reached through the main api-server (in its mode as a proxy for the aggregated api-server, in which it uses a single HTTP/2 connection for all calls proxied to that aggregated api-server). Fixes #60042		2018-02-22 16:31:21 -05:00
..
BUILD	Autogenerated: hack/update-bazel.sh	2018-02-16 13:43:01 -08:00
options.go	controller-manager: add SecureServingOptions	2018-02-13 11:16:47 +01:00
options_test.go	Fixes for HTTP/2 max streams per connection setting	2018-02-22 16:31:21 -05:00