Discusses the current security risks posed by the kubelet->etcd pattern
and discusses some options.

Triggered by #846 and referenced in #859

Fix local-docker KUBERNETES_MASTER

Don't use pointers for session affinity

Minor cleanups to request - fix initialism on HTTPClientFunc

Default behavior for "" is already "everything"

Add a util/mount pkg

Introduce Resource/ResourceName/Prefix/Suffix options to RESTClient

Remove duplicate volumes type.

Update doc volumes.md to make sure mount point is created before mountin...

Modify "kubectl get events" to print FieldPath so BoundPod events for the same pod but different containers can be differentiated

Modify "kubectl get events" to print FieldPath so BoundPod events for the same Pod but different containers can be differentiated

Propagate syncPod error as event to upper layer.

Add missign network flag

Fix proxy bug where it lies about encoding

RESTClient is an abstraction for simplifying access to resources that
follow the Kubernetes API pattern.  Currently, both Namespace and Path
are coupled, which means changes across versions is complex.  In general,
most access to resources should be to a resource collection (e.g.
"services") with a name (e.g. "foo"). Other constructs, like prefix sections
("watch") or proposed suffix sections ("/pods/foo/spec") only modify this
core pattern.

This commit removes the Path() helper from Request and introduces:

* Prefix(segments ...string) - segments that should go to the beginning of the path.
* Suffix(segments ...string) - segments that should go to the end of the path.
* Resource(string) - collection name, should be after prefix
* Namespace(string) - if specified, should be set after resource but before name
* Name(string) - if specified, should be after namespace

Now, only Prefix and Suffix are order dependent (and with variadics, should be
simpler).  Resource, Namespace, and Name may be specified in any order.

Path() has been removed to prevent downstream consumers of RESTClient from experiencing
behavior change.

Allow --api-version to properly override various default behaviors in CLI

Added test cases for NewKubeletClient with TLS enabled

Have Http Liveness Probe report "Unhealthy" on connection failure instead of "Unknown"

Solve apt-get update 404 Not Found Package error

Enable DNS for services

"kind" is needed to start the pod

Added config note for ssh root logins.

Remove erroneous . from wget commands

Scheduler is printing the wrong value when no default algorithms available

wget always downloads into current directory

After this DNS is resolvable from the host, if the DNS server is targetted
explicitly.  This does NOT add the cluster DNS to the host's resolv.conf.  That
is a larger problem, with distro-specific tie-ins and circular deps.

Rather than have to keep SkyDNS up to date with Kubernetes, use a
buddy-container "kube2sky" to watch kubernetes and sync Service records
into etcd for SkyDNS ot find.  This also adds namespace support.

This adds --cluster_dns and --cluster_domain flags to kubelet.  If
non-empty, kubelet will set docker --dns and --dns-search flags based on
these.  It uses the cluster DNS and appends the hosts's DNS servers.
Likewise for DNS search domains.

This also adds API support to bypass cluster DNS entirely, needed to
bootstrap DNS.