enable all experimental controllers in controller-manager with one flag

Auto commit by PR queue bot

Add an environment variable override for AWS ssh keys

Implemented e2e test for Initial Resources

Auto commit by PR queue bot

Check for number of scheduled, not running nodes in scheduler_predicates test

Unset NUM_MINIONS variable in Kubemark Jenkins run, to allow use of Kubemark default

Wait for all HollowNodes to become ready in start-kubemark.sh

Auto commit by PR queue bot

Auto commit by PR queue bot

break up daemonset test into two small tests to isolate flakiness

Auto commit by PR queue bot

Write log if two replication controller overlap

Also enable this option in our Jenkins runs.

Multiple rbd volume enhancements

examples/vitess: Update for Vitess v2.0.0-alpha3

kubectl get jobs printing fix

Turn on smarter FakeDockerClient in HollowNode.

MESOS: bugfix, configure oomAdjuster so that it gets passed on to the kubelet

Wait longer for job to complete

Fix documentation in clientcmd/doc.go.

AWS: Create DHCP Option Set on kube-up

expose: Truncate service names

Move events to a separate etcd instance

Unrevert #14608 and decrease the latency of GCE load balancer deletions

This will cut down on the amount of time it takes to delete an external
load balancer, which should reduce the likelihood of resource leaks when
clusters are deleted.

as goroutines, blocks until they're all done executing, and combines the
results into an Aggregate error.

This code was in rough shape, so I've fixed the issues with the original
PR as well as a few other changes:
1. Clarify the error messages related to the "gce Addresses" to make it
   clear we're talking about static IP addresses
2. Fix the bug in the original PR, which was a nil pointer dereference
   from passing op to waitForRegionOp when the address doesn't exist.
3. Rearrange the steps of EnsureTCPLoadBalancerDeleted to be the reverse
   of EnsureCreated, which mostly just seems like good practice to me.
   This is also supported by the following two bugs I found :(
4. Fix an independent bug of returning too early if the target pool
   doesn't exist, effectively stranding the firewall. This was likely
   introduced because target pools used to be the last thing deleted,
   so it was previously safe to return there.
5. Fix an independent bug of not returning an error waiting for the
   target pool to be deleted failed. This was very possibly causing
   target pool leaks in our e2e tests. This was similarly due to
   assuming that the target pool was the last thing deleted in the
   function, then having the firewall deletion stuck in after it.

Services e2e cleanup

Record pod history in daemon restart e2e

Pod level SELinux context and volumes