Add docs for ubuntu kubernetes cluster upgrading

Fix indendation on devel/coding-conventions.md

Correct comments in mount.go

Fix document link

change etcdIndec to etcdIndex

Bump Container Inspect to loglevel 4

fix the parameter name of k8s version

Use the cluster name instead of the minion tag as the prefix for the firewall rules created in gke e2e tests

change kubernetes-mininon to kubernetes-node

updating label selector doc

Revert "Check the condition immediately in util.Wait funcs"

Check the condition immediately in util.Wait funcs

Vagrant salt-minion should have low oom_score_adj and restart policy

Flag controlled RLIMIT_NOFILE for kubelet.

Change a describe in docs/design/secrets.md

Fix minor error in Pod introduction

[libvirt-coreos cluster] Get rid of the etcd discovery mechanism in favor of static configuration

change minion to node

Unit tests for metrics_client.go

Remove dead RateLimit function from API server handlers

Avoid assumption of a fixed list of cgroups in e2e conformance tests

Replace testDocker with container.fakeRuntime in runonce_test

build: fix link syntax in README

hack/verify-all.sh return error on errors

Add link to dev e2e docs from api_changes doc

Increase a bunch of timeouts to reduce flakes

Functionally revert #12894

WaitForService added to autoscaling_utils.go

runonce_test should not be testing docker-specific logic.

Signed-off-by: Sami Wagiaalla <swagiaal@redhat.com>

Other cluster provider than gce or gke might have different cgroup layouts.
From outside we cannot know how these look like (especially in conformance test
which do not know the cluster provider at all).

Hence, this PR defaults to only the "/" cgroup to collect stats for. In the case
of gce or gke the full container list is tested.

Fixes https://github.com/mesosphere/kubernetes-mesos/issues/436

As discussed @gmarek the given test does not belong into the conformance test
suite because it makes a lot of static assumptions about the cgroup setup of the
nodes which cannot be fulfilled by all cluster providers. Depending on the
installation the kubelet is not allowed to move around process
into specific containers.

Fixes https://github.com/mesosphere/kubernetes-mesos/issues/439.