Remove unnecessary bind-mount from dockerized kubelet run

Fix OpenShift example

API Server - pass path name in context of create request for subresource

Rolling Updates: Add support for --rollback.

Allows a REST storage for a subresource to obtain name in path from
request.

Beef up services doc a little

Support manually-created and generated conversion functions

Update to container-vm-v20150505 (Also updates GCE to Docker 1.6)

Kubelet: record the timestamp correctly in the runtime cache

Fix metric label

Also push .sha1 for devel builds

Convert examples to v1beta3, flesh out some details, mention L7.

Update volumes doc to fix broken link and describe new file.

Fix v1beta1 typos in v1beta2 conversions

Fix link to service accounts doc in security context doc

Add ability to dockerize kubelet in local cluster

skydns: use the etcd-2.x native syntax, enable IANA attributed ports.

Added port 6443 to kube-proxy default IP address for api-server

Added client header info for authentication doc.

added  api_servers_with_port variable and settings.

removed extra port string

split azure api_server host and port out

per https://github.com/coreos/etcd/blob/master/Documentation/backward_compatibility.md
(there are no functional changes, we just stop using the legacy flags, for
consistency.)
Signed-off-by: António Meireles <antonio.meireles@reformi.st>

Clean up safe_format_and_mount spam in the startup logs

Signed-off-by: Rodolfo Carvalho <rcarvalh@redhat.com>

update AWS CloudFormation template and cloud-configs

Create docker image for kubelet

kubelet/rkt: Add docker prefix to image string.

Set allocate_node_cidrs to be blank by default.

Fix sync problems in #5246

Totally minor cleanup, but I'm tired of seeing it's spam in the
startup logs.

If a pod worker sees stale pods from the runtime cache which were retrieved
before their last sync finished, it may think that the pod were not started
correctly, and attemp to fix that by killing/restarting containers.
There are two issues that may cause runtime cache to store stale pods:
  1. The timstamp is recorded *after* getting the pods from the container
     runtime. This may lead the consumer to think the pods are newer than they
     actually are.
  2. The cache updates are triggered by many goroutines (pod workers, and the
     updating thread). There is no mechanism to enforece that the cache would
     only be updated to newer pods.

This change fixes the above two issues by making sure one always record the
timestamp before getting pods from the container runtime, and updates the
cached pods only if the timestamp is newer.