anchor.diff:  
   == Overview
   
  -OpenShift takes advantage of a feature built into Kubernetes to support
  -executing commands in containers. This is implemented using HTTP along with a
  -multiplexed streaming protocol such as link:http://www.chromium.org/spdy[SPDY]
  -or link:https://http2.github.io/[HTTP/2].
  +OpenShift takes advantage of a feature built into Kubernetes to support port
  +forwarding to pods. This is implemented using HTTP along with a multiplexed
  +streaming protocol such as link:http://www.chromium.org/spdy[SPDY] or
  +link:https://http2.github.io/[HTTP/2].
   
   === Client Operation
   
  
positive.code: * `node123.openshift.com` is the node name
  * `myns` is the target pod's namespace
  * `mypod` is the target pod's name
  * `mycontainer` is the target container's name
  
  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 SPDY.
  
  The client creates a stream with the `port` header containing the target port
  in the container. All data written to the stream is delivered via the Kubelet
  to the target container and port. Similarly, all data sent from the container
  for that forwarded connection is delivered back to the same stream in the
  client.
  
  The client should close all streams, the upgraded connection, and the
  underlying connection when it is finished with the port forwarding request.
  
negative.code: Support for port forwarding is built into `kubectl`:
  
  ----
  kubectl port-forward -p <pod> [<local port:]<pod port> [[<local port:]<pod port> ...]
  ----
  
  Kubectl listens on each local port specified by the user, forwarding via the
  