Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:10:32Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: VMware, 1c/4t, 8GB, HDD

OS (e.g. from /etc/os-release): Red Hat Enterprise Linux Server release 7.2 (Maipo)

Kernel (e.g. uname -a):3.10.0-327.el7.x86_64

Install tools: yum install -y docker kubelet kubeadm kubectl kubernetes-cni

Others:

# docker version
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:11 2016
OS/Arch: linux/amd64

Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:11 2016
OS/Arch: linux/amd64

# kubectl get nodes
NAME STATUS AGE
kubernetes01.raiffeisen.pl Ready 21d
kubernetes02.raiffeisen.pl Ready 21d
kubernetes03.raiffeisen.pl Ready 21d

What happened: According to doc's (http://kubernetes.io/docs/getting-started-guides/kubeadm/) I should be able to run cluster, run pod's and access web UI. UI is unaccessible:

WebUI:

http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard

output in browser:

{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "no endpoints available for service \"kubernetes-dashboard\"",
"reason": "ServiceUnavailable",
"code": 503
}

cAdvisor is working fine.

# kubectl get pods --all-namespaces --show-all
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system etcd-kubernetes01.raiffeisen.pl 1/1 Running 4 21d
kube-system kube-apiserver-kubernetes01.raiffeisen.pl 1/1 Running 6 21d
kube-system kube-controller-manager-kubernetes01.raiffeisen.pl 1/1 Running 4 21d
kube-system kube-discovery-982812725-7l2xu 1/1 Running 0 49m
kube-system kube-discovery-982812725-iju5t 0/1 MatchNodeSelector 0 21d
kube-system kube-dns-2247936740-6wc33 0/3 ContainerCreating 0 21d
kube-system kube-proxy-amd64-g7b7b 1/1 Running 4 21d
kube-system kube-proxy-amd64-npjme 1/1 Running 4 21d
kube-system kube-proxy-amd64-o6cb7 1/1 Running 4 13d
kube-system kube-scheduler-kubernetes01.raiffeisen.pl 1/1 Running 4 21d
kube-system kubernetes-dashboard-1655269645-m37rm 0/1 ContainerCreating 0 44m
sock-shop cart-2013512370-opewy 0/1 ContainerCreating 0 40m
sock-shop cart-db-1445314776-datu9 0/1 ContainerCreating 0 40m
sock-shop catalogue-3777349842-0kxk4 0/1 ContainerCreating 0 40m
sock-shop catalogue-db-2196966982-90h70 0/1 ContainerCreating 0 40m
sock-shop front-end-697319832-zv5j4 0/1 ContainerCreating 0 40m
sock-shop orders-3580282209-vu30j 0/1 ContainerCreating 0 40m
sock-shop orders-db-1215677090-n6kvx 0/1 ContainerCreating 0 40m
sock-shop payment-1376044718-lhe69 0/1 ContainerCreating 0 40m
sock-shop queue-master-1190579278-xgv56 0/1 ContainerCreating 0 40m
sock-shop rabbitmq-1897447621-u70le 0/1 ContainerCreating 0 40m
sock-shop shipping-589875162-h7ir9 0/1 ContainerCreating 0 40m
sock-shop user-3338781425-mm6sk 0/1 ContainerCreating 0 40m
sock-shop user-db-710789251-gtpx5 0/1 ContainerCreating 0 40m

What you expected to happen: I was expecting to access web UI and at least install sample appication (sock-shop). Failed at both. sock-shop PODs are not showing any logs. Same for docker. Sock-shop hangs at "ContainerCreating".

Issue 2:
I was mostly following this guide, which seems to be either deprecated and/or broken:

https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/ubuntu.md

One key bug, one of the scripts references the wrong Github account, fix:

diff --git a/cluster/ubuntu/download-release.sh b/cluster/ubuntu/download-release.sh
index 3fce5d0..5fb3ea1 100755
--- a/cluster/ubuntu/download-release.sh
+++ b/cluster/ubuntu/download-release.sh
@@ -56,7 +56,7 @@ grep -q "^${ETCD_VERSION}\$" binaries/.etcd 2>/dev/null || {
KUBE_VERSION=${KUBE_VERSION:-"1.1.2"}
echo "Prepare kubernetes ${KUBE_VERSION} release ..."
grep -q "^${KUBE_VERSION}\$" binaries/.kubernetes 2>/dev/null || {
- curl -L https://github.com/GoogleCloudPlatform/kubernetes/releases/download/v${KUBE_VERSION}/kubernetes.tar.gz -o kubernetes.tar.gz
+ curl -L https://github.com/kubernetes/kubernetes/releases/download/v${KUBE_VERSION}/kubernetes.tar.gz -o kubernetes.tar.gz
tar xzf kubernetes.tar.gz
pushd kubernetes/server
tar xzf kubernetes-server-linux-amd64.tar.gz

But I still can't kube-up.sh:

$ export KUBE_VERSION=1.1.2
$ export KUBERNETES_PROVIDER=ubuntu

$ export nodes="root@10.0.10.xxx root@10.0.10.yyy"
$ export roles="ai i"
$ export NUM_MINIONS=2
$ export PATH=$PATH:~pwais/kubernetes/cluster/ubuntu/binaries

$ ./cluster/kube-up.sh
... Starting cluster using provider: ubuntu
... calling verify-prereqs
... calling kube-up
/home/pwais/kubernetes/cluster/ubuntu /home/pwais/kubernetes
Prepare flannel 0.5.0 release ...
Prepare etcd 2.2.0 release ...
Prepare kubernetes 1.1.2 release ...
Done! All your binaries locate in kubernetes/cluster/ubuntu/binaries directory
/home/pwais/kubernetes

Deploying master and node on machine 10.0.10.240
saltbase/salt/generate-cert/make-ca-cert.sh: No such file or directory
config-default.sh 100% 3441 3.4KB/s 00:00
ubuntu/util.sh: No such file or directory
ubuntu/minion/*: No such file or directory
ubuntu/master/*: No such file or directory
ubuntu/reconfDocker.sh: No such file or directory
ubuntu/binaries/master: No such file or directory
ubuntu/binaries/minion: No such file or directory

I had more luck with v1.0.0 except that kube-proxy failed to launch on my minion because of an incorrect flag to the executable :P

If somebody can direct me to a bona fide Ubuntu bare-metal setup guide, please LMK. Otherwise I guess I'll try to poke at master a bit more (and perhaps contribute a patch if I get anywhere).