Ubernetes-Lite GCE: Label volumes with zone information

ScheduledJob controller proposal

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

Disabled cluster size autoscaling e2e since they are flaky

Dedicated nodes, taints, and tolerations design proposal

Node affinity and NodeSelector design doc

How to build Mesos/Omega-style frameworks on Kubernetes.

fix nil pointer in addons test

move spark images to github.com/kubernetes/application-images/spark

Handle multijob runners properly in verify-jenkins-jobs.sh

Remove TestWatchEtcdError

slightly better logs in service e2e

cluster/gce: fix unbound variable

Make ServiceLoadBalancer a Feature test

Add time logging to runReplicationControllerTest to help debug timeouts in the future

We decided to remove this test, as there's no way to get an upper bound
on its running time. Etcd restart behavior should be tested in
integration or e2e tests.

timeouts in the future.

Revert "kubectl: Make scaling smarter"

19848: Retry service IP repair on conflict

When job.spec.completions is nil, only
one task needs to succeed for the job to succeed,
and parallelism can be scaled freely during runtime.

Added tests.

Release Note:

This causes two minor changes to the API.

First, unset parallelism previously was defaulted to be
equal to completions.  Now it always defaults to 1 if unset.

Second, having parallelism=N and completions unset would previously
be defaulted to 1 completion and N parallelism.
(this is not something we expect people to do, though)
Now, no defaulting occurs in that case, and the job's
behavior is different (any completion causes success).

build: Use Go version in cross image tag

We don't cope well if a PD is in multiple zones, but this is actually
fairly easy to detect.  This is probably justified purely on the basis
that we never want to delete the wrong volume (DeleteDisk), but also
because this means that we now warn on creation if a disk is in multiple
zones (with the labeling admission controller).

This also means that with the scheduling predicate in place, that many
of our volume problems "go away" in practice: you still can't create or
delete a volume when it is ambiguous, but thereafter the volume will be
labeled with the zone, that will match it only to nodes with the same
zone, and then we query for the volume in that zone when we
attach/detach it.