Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Sometimes the test server would close down the TCP socket before all
requests could finish.

Auto commit by PR queue bot

Auto commit by PR queue bot

api server library: moving API registration logic to generic api server

Adding instructions to run versionize-docs in cherrypick doc

Auto commit by PR queue bot

Relisting latency/interval affects how quick kubelet discovers changes. Record
the metrics in Prometheus to surface such information.

Add sleep to EtcdTestServer Terminate.

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

If a route already exists but is invalid (e.g. from a crash), we
automatically delete it before trying to create a route that would
otherwise conflict.

Auto commit by PR queue bot

Add node-ip flag to know-flags.txt

In case of multiple IPs on the node, this will allow admin to
specify desired IP to be used for the node.

Auto commit by PR queue bot

Auto commit by PR queue bot

Fix TestPoll test

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

It fix this bug :
https://stackoverflow.com/questions/34255601/kube-addons-service-failed-on-coreos-libvirt-installation

Some documentation that explain why clusterIP is better :
https://github.com/kubernetes/kubernetes/blob/master/docs/api.md

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Updage auto-generated files

For AWS EBS, a volume can only be attached to a node in the same AZ.
The scheduler must therefore detect if a volume is being attached to a
pod, and ensure that the pod is scheduled on a node in the same AZ as
the volume.

So that the scheduler need not query the cloud provider every time, and
to support decoupled operation (e.g. bare metal) we tag the volume with
our placement labels.  This is done automatically by means of an
admission controller on AWS when a PersistentVolume is created backed by
an EBS volume.

Support for tagging GCE PVs will follow.

Pods that specify a volume directly (i.e. without using a
PersistentVolumeClaim) will not currently be scheduled correctly (i.e.
they will be scheduled without zone-awareness).

Auto commit by PR queue bot