Remove redundant RC and service tests in integration.go

Upgrade installed packages when building hyperkube to improve the security profile

Never leak the etcd watcher's translate goroutine

Proper account checking and respect TMPDIR in release process

fix config view output bug

reuse goproxy pod and avoid race between kubectl exec and goproxy readiness

fix immediate evict in cache

improve the osx build experience

e2e_node: Disable auto restart on CoreOS.

Use fake clock in TestGetPodsToSync.

kubectl: remove dead factory code

kubelet: do not force update the runtime cache

Fix incorrect comments in IsPodAvailable

allow equality to avoid flaky on clock

mark container-port flag as deprecated

Move getCloudProvider retries to getCloudProvider()

Handle possible error in client reflector run loops

Make fake event recorder thread safe.

GCI/Trusty: Support ABAC authorization

add cni plugins to hyperkube image

Update Heapster api types location in Godeps

Allow test-cmd to run on non-Linux OS

fix cinder volume dir umount issue #24717

Clarify orphaned volume cleanup

Make threadSafeMap.ListIndexFuncValues thread safe.

rkt: When host port is zero, we should not forward the port.

Trace.Step() performs an unnecessary alloc

mungedocs should not assume upstream remote

Fix SELinux settings for mounted volumes

Revert "Always use long format in git tag."

Add missing "--test" flag to conformance test instructions.

Fix function name typo in kubelet

Fix node e2e startServer failure output

kubectl: use platform-agnostic helper in edit

Automatic merge from submit-queue

Define interfaces for kubelet pod admission and eviction

There is too much code and logic in `kubelet.go` that makes it hard to test functions in discrete pieces.

I propose an interface that an internal module can implement that will let it make an admission decision for a pod.  If folks are ok with the pattern, I want to move the a) predicate checking, b) out of disk, c) eviction preventing best-effort pods being admitted into their own dedicated handlers that would be easier for us to mock test.  We can then just write tests to ensure that the `Kubelet` calls a call-out, and we can write easier unit tests to ensure that dedicated handlers do the right thing.

The second interface I propose was a `PodEvictor` that is invoked in the main kubelet sync loop to know if pods should be pro-actively evicted from the machine.  The current active deadline check should move into a simple evictor implementation, and I want to plug the out of resource killer code path as an implementation of the same interface.

 @vishh @timothysc - if you guys can ack on this, I will add some unit testing to ensure we do the call-outs.

/cc @kubernetes/sig-node @kubernetes/rh-cluster-infra 

Allocates more objects than necessary.

Automatic merge from submit-queue

Avoid allocations and a reflect.Call in conversion

reflect.Call is fairly expensive, performing 8 allocations and having to
set up a call stack. Using a fairly straightforward to generate switch
statement, we can bypass that early in conversion (as long as the
function takes responsibility for invocation). We may also be able to
avoid an allocation for the conversion scope, but not positive yet.

```
benchmark                    old ns/op     new ns/op     delta
BenchmarkPodConversion-8     14713         12173         -17.26%

benchmark                    old allocs     new allocs     delta
BenchmarkPodConversion-8     80             72             -10.00%

benchmark                    old bytes     new bytes     delta
BenchmarkPodConversion-8     9133          8712          -4.61%
```

@wojtek-t related to #20309

Automatic merge from submit-queue

kubenet: fix up CNI bridge TX queue length if needed

CNI's bridge plugin mis-handles the TxQLen when creating the bridge,
leading to a zero-length TX queue.  This doesn't typically cause
problems (since virtual interfaces don't have hard queue limits)
but when adding traffic shaping, some qdiscs pull their packet
limits from the TX queue length, leading to a packet limit of 0
in some cases.  Until we can depend on a new enough version of
CNI, fix up the TX queue length internally.

Closes: https://github.com/kubernetes/kubernetes/issues/25092

Automatic merge from submit-queue

e2e: Enable persistent volume test

The test is already there and all packages should be already available on all test machines.
    
It tests:

- binding
- using bound claim in a pod
- recycling NFS volume

(we should see shortly if all nfs packages are really installed as Jenkins tests it...)