Merge pull request #45734 from stevsmit/GH45628

Swaps references of SPDY with HTTP2

Author: stevsmit

modules/migration-configuring-proxies.adoc

@@ -13,7 +13,7 @@ For {product-title} 4.1 and earlier versions, you must configure proxies in the
 
 For {product-title} 4.2 to {product-version}, the {mtc-full} ({mtc-short}) inherits the cluster-wide proxy settings. You can change the proxy parameters if you want to override the cluster-wide proxy settings.
 
-You must configure the proxies to allow the SPDY protocol and to forward the `Upgrade HTTP` header to the API server. Otherwise, an `Upgrade request required` error is displayed. The `MigrationController` CR uses SPDY to run commands within remote pods. The `Upgrade HTTP` header is required in order to open a websocket connection with the API server.
+You must configure the proxies to allow the `HTTP/2` protocol and to forward the `Upgrade HTTP` header to the API server. Otherwise, an `Upgrade request required` error is displayed. The `MigrationController` CR uses `HTTP/2` to run commands within remote pods. The `Upgrade HTTP` header is required in order to open a websocket connection with the API server.
 
 .Direct volume migration
 

modules/nodes-containers-port-forwarding-protocol.adoc

@@ -3,7 +3,7 @@
 // * nodes/nodes-containers-port-forwarding.adoc
 
 [id="nodes-containers-port-forwarding-protocol_{context}"]
-= Protocol for initiating port forwarding from a client 
+= Protocol for initiating port forwarding from a client
 
 Clients initiate port forwarding to a pod by issuing a request to the
 Kubernetes API server:
@@ -26,7 +26,7 @@ For example:
 
 After sending a port forward request to the API server, the client upgrades the
 connection to one that supports multiplexed streams; the current implementation
-uses link:http://www.chromium.org/spdy[*SPDY*].
+uses link:https://httpwg.org/specs/rfc7540.html[*Hyptertext Transfer Protocol Version 2 (HTTP/2)*].
 
 The client creates a stream with the `port` header containing the target port in
 the pod. All data written to the stream is delivered via the kubelet to the
@@ -35,4 +35,3 @@ connection is delivered back to the same stream in the client.
 
 The client closes all streams, the upgraded connection, and the underlying
 connection when it is finished with the port forwarding request.
-

modules/nodes-containers-remote-commands-protocol.adoc

@@ -37,7 +37,7 @@ Additionally, the client can add parameters to the request to indicate if:
 
 After sending an `exec` request to the API server, the client upgrades the
 connection to one that supports multiplexed streams; the current implementation
-uses *SPDY*.
+uses *HTTP/2*.
 
 The client creates one stream each for stdin, stdout, and stderr. To distinguish
 among the streams, the client sets the `streamType` header on the stream to one