anchor.diff:  
   Ports may be specified using the following formats:
   
  -* `5000` - the client listens on port 5000 locally and forwards to 5000 in the container
  -* `6000:5000` - the client listens on port 6000 locally and forwards to 5000 in the container
  -* `:5000` or `0:5000` - the client selects a free local port and forwards to 5000 in the container
  +* `5000` - the client listens on port 5000 locally and forwards to 5000 in the pod
  +* `6000:5000` - the client listens on port 6000 locally and forwards to 5000 in the pod
  +* `:5000` or `0:5000` - the client selects a free local port and forwards to 5000 in the pod
   
   ==== Protocol
   
  -Clients initiate the execution of a remote command in a container by issuing a
  -request to the Kubernetes API Server:
  +Clients initiate port forwarding to a pod by issuing a request to the
  +Kubernetes API Server:
   
   ----
  -/proxy/minions/node123.openshift.com/portForward/myns/mypod/mycontainer
  +/proxy/minions/node123.openshift.com/portForward/myns/mypod
   ----
   
   In the above URL:
  
positive.code: 
  == 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].
  
  === Client Operation
  
  
negative.code: * `node123.openshift.com` is the node name
  * `myns` is the target pod's namespace
  * `mypod` is the target pod'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 pod. All data written to the stream is delivered via the Kubelet to the
  target pod and port. Similarly, all data sent from the pod 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.
  