Changes to make kube-proxy userspace scale better

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Add cpu/mem reservation metrics for autoscaler in kube-up

Fix terminated pod printing in kubectl describe

Fixed panic in autoscaling e2e tests

Initial Kubemark commit

Added debug logs to autoscaling_utils.go

Disable kubelet_perf test in GKE

In upstream the kubelet is responsible for all pods which have the spec.NodeName
set. In Mesos we have a two-stage scheduling process:

1. pods with a pre-set spec.NodeName are still scheduled by the scheduler.
2. The kubelet will only see them when a Mesos task was started and the executor
   passes the pod to the kubelet.

With this PR a pod with spec.NodeName which is gracefully terminated, but not
yet scheduled, e.g.

- because the termination happened just after creation and the scheduler was
  not fast enough
- because the NodeSelector does not match

is deleted by the Mesos scheduler.

We can assume that n != nil holds, because otherwise offers are skipped.

- pre-create node api objects from the scheduler when offers arrive
- decline offers until nodes a registered
- turn slave attributes as k8s.mesosphere.io/attribute-* labels
- update labels from executor Register/Reregister
- watch nodes in scheduler to make non-Mesos labels available for NodeSelector matching
- add unit tests for label predicate
- add e2e test to check that slave attributes really end up as node labels

Revert "Maintain an IP address independent of the forwarding rule for…

Describe more clearly

Lengthen integration test timeout

Add a munger check for files that end in preformat