Changes

Added IPv6 support for the ipfailover keepalived image.  - Added IPv6
Address support  - Added IPv6 Address Range Support  - Added IPv6
Address Validation  - Added IPv4 Address Validation  - Added relevant
test cases
Defined all function variables as local
 (commit: c5f949b)

UPSTREAM: 45049: Log an EBS vol's instance when attaching fails because
VolumeInUse
 (commit: 4368897)

UPSTREAM: 44579: make certs used in roundtripper_test same as those used
in proxy_test
 (commit: 9f5cd22)

UPSTREAM: 44583: bump bazel build to go1.8.1 and remove invalid unit
tests
 (commit: a2e728b)

UPSTREAM: 41758: Updated key.pm and cert.pm to remove error in setting
up localhostCert pool
 (commit: 0aecbd5)

UPSTREAM: 46440: fix api server handler routing (move CRD behind TPR)
 (commit: a690456)

sdn: kill containers that fail to update on node restart
With the move to remote runtimes, we can no longer get the pod's network
namespace from kubelet (since we cannot insert ourselves into the remote
runtime's plugin list and intercept network plugin calls).  As kubelet
does not call network plugins in any way on startup if a container is
already running, we have no way to ensure the container is using the
correct NetNamespace (as it may have changed while openshift-node was
down) at startup, unless we encode the required information into OVS
flows.
But if OVS was restarted around the same time OpenShift was, those flows
are lost, and we have no information with which to recover the pod's
networking on node startup.  In this case, kill the infra container
underneath kubelet so that it will be restarted and we can set its
network up again.
NOTE: this is somewhat hacky and will not work with other remote 
runtimes like CRI-O, but OpenShift 3.6 hardcodes dockershim so this 
isn't a problem yet.  The "correct" solution is to either checkpoint our
network configuration at container setup time and recover that 
ourselves, or to add a GET/STATUS call to CNI and make Kubelet call that
operation on startup when recovering running containers.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1453113
 (commit: fd6dee8)

UPSTREAM: <drop>: Use Clone for CloneTLSConfig for golang 1.8
Use Clone() for the implementation of CloneTLSConfig when golang version 
is 1.8, otherwise continue to use existing implementation. This avoids 
issues related Clone() calling serverInit on the source object if it was 
not already previously run.
This ensures that CloneTLSConfig is able to be used consistently for 
both golang 1.7 and golang 1.8.
This commit can be dropped when rebased on k8s 1.7, which will require 
golang 1.8. Alternatively, this commit can be dropped if we move to 
golang 1.8 exclusively and the related upstream Clone() changes are 
backported.
 (commit: 868a91a)