Automatic merge from submit-queue client-go PortForwarder: don't log an error if net.Listen fails **What this PR does / why we need it**: If ipv6 is disabled the client-go PortForwarder logs an error: ``` E0406 17:26:06.983609 29625 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:30143: socket: address family not supported by protocol ``` This pull request removes this error log. Reasons: * Tunnel creation might still succeed on ipv4 and the error just confuses the user (see https://github.com/kubernetes/helm/issues/2223). * If the tunnel can't be created the error gets also loggen in `listenOnPort`. * runtime.HandleError should only be used on errors "_when a non-user facing piece of code cannot return an error"_ which isn't the case here. **Which issue this PR fixes** Fixes https://github.com/kubernetes/helm/issues/2223
This staging/src/k8s.io/client-go directory is the staging area of the client repo. It contains a versioned client, tools built around the client like the reflector, and all the client dependencies. The content will be periodically published to k8s.io/client-go repo.
The staged content is copied from the main repo, i.e., k8s.io/kubernetes, with directory rearrangement and necessary rewritings. To sync the content with the latest code in your local k8s.io/kubernetes, you need to run godep restore in k8s root directory, then run staging/copy.sh.
vendor/k8s.io/client-go is a symlink pointing to this staging area, so to use the packages in the staging area, you can import it as "vendor/client-go/", as if the client were vendored. The client will be vendored from k8s.io/client-go for real after the test matrix is converted to vendor k8s components.