Kubelet: surface the container creation/start failure reason

kube-apiserver in a pod.

Add to controller framework; use in scheduler

Fix heapster config to talk to the right kubelet port.

Container creation/start failure cannot be reproduced by inspecting the
containers. This change caches such errors so that kubelet can retrieve it
later.

This change also extends FakeDockerClient to support setting error response
for a specific function.

The config was updated for v1bet1, but the tests are using v1beta3.

Fix printing errors from failed binary runs

Update to storm example

I had the kublet die on startup and the only error was "0x401da0"  Which
I assume is an address of the err.Error function.  The other way to fix
this, I think, would be to use err.Error(), however that could cause
fmt.Fprintf() problems, debuging on the error message people used.

Now I get a nice clean error I can understand:

"cAdvisor.New() err = mountpoint for cpu not found"

Remove nodeinfo endpoint from kubelet

Fix a small regression on api server proxy after switch to v1beta3.

Also add tests; coverage up to 86.7%

Add DeepCopy! Also-- optimize conversion for []byte

Local-up-cluster does not have admission control

AWS EBS volume support

Enable pprof on the kube-proxy's healthz http server.

Small fix for secret doc

Default replica controller selector and labels using pod template.