5 Commits (e2893bbc949b48f81b3690cb47123a959606f5bc)

Author	SHA1	Message	Date
Michael Fraenkel	93c11422e4	CRI Portforward needs to forward websocket ports ... - adjust ports to int32 - CRI flows the websocket ports as query params - Do not validate ports since the protocol is unknown SPDY flows the ports as headers and websockets uses query params - Only flow query params if there is at least one port query param	2017-02-01 18:03:42 -07:00
Michael Fraenkel	beb53fb71a	Port forward over websockets ... - split out port forwarding into its own package Allow multiple port forwarding ports - Make it easy to determine which port is tied to which channel - odd channels are for data - even channels are for errors - allow comma separated ports to specify multiple ports Add portfowardtester 1.2 to whitelist	2017-02-01 06:32:04 -07:00
Dr. Stefan Schimanski	674d78b2ab	pkg/util: move httpstream to k8s.io/apimachinery	2017-01-27 15:10:42 -05:00
deads2k	6a4d5cd7cc	start the apimachinery repo	2017-01-11 09:09:48 -05:00
Tim St. Clair	52ed57ec3b	Refactor PortForward server methods into the portforward package	2016-10-25 12:08:35 -07:00