Commit 5d6b8d7d authored by Daniel Smith's avatar Daniel Smith

doc updates

parent 3f454b75
...@@ -87,7 +87,7 @@ what etcd offers (at least not in the way we use it). For simplicty, we run ...@@ -87,7 +87,7 @@ what etcd offers (at least not in the way we use it). For simplicty, we run
etcd and SkyDNS together in a pod, and we do not try to link etcd instances etcd and SkyDNS together in a pod, and we do not try to link etcd instances
across replicas. A helper container called [kube2sky](kube2sky/) also runs in across replicas. A helper container called [kube2sky](kube2sky/) also runs in
the pod and acts a bridge between Kubernetes and SkyDNS. It finds the the pod and acts a bridge between Kubernetes and SkyDNS. It finds the
Kubernetes master through the `kubernetes-ro` service (via environment Kubernetes master through the `kubernetes` service (via environment
variables), pulls service info from the master, and writes that to etcd for variables), pulls service info from the master, and writes that to etcd for
SkyDNS to find. SkyDNS to find.
......
...@@ -20,5 +20,5 @@ spec: ...@@ -20,5 +20,5 @@ spec:
name: heapster name: heapster
command: command:
- /heapster - /heapster
- --source=kubernetes:http://kubernetes-ro?auth= - --source=kubernetes:http://kubernetes?auth=
- --sink=influxdb:http://monitoring-influxdb:8086 - --sink=influxdb:http://monitoring-influxdb:8086
...@@ -116,7 +116,6 @@ POD IP CONTAINER(S) IMAGE(S) HOST LABELS ...@@ -116,7 +116,6 @@ POD IP CONTAINER(S) IMAGE(S) HOST LABELS
$ bin/kubectl get services # your service IPs will likely differ $ bin/kubectl get services # your service IPs will likely differ
NAME LABELS SELECTOR IP PORT NAME LABELS SELECTOR IP PORT
kubernetes component=apiserver,provider=kubernetes <none> 10.10.10.2 443 kubernetes component=apiserver,provider=kubernetes <none> 10.10.10.2 443
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.10.10.1 80
``` ```
Lastly, use the Mesos CLI tool to validate the Kubernetes scheduler framework has been registered and running: Lastly, use the Mesos CLI tool to validate the Kubernetes scheduler framework has been registered and running:
```bash ```bash
...@@ -241,7 +240,6 @@ Next, determine the internal IP address of the front end [service][8]: ...@@ -241,7 +240,6 @@ Next, determine the internal IP address of the front end [service][8]:
$ bin/kubectl get services $ bin/kubectl get services
NAME LABELS SELECTOR IP PORT NAME LABELS SELECTOR IP PORT
kubernetes component=apiserver,provider=kubernetes <none> 10.10.10.2 443 kubernetes component=apiserver,provider=kubernetes <none> 10.10.10.2 443
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.10.10.1 80
redismaster <none> name=redis-master 10.10.10.49 10000 redismaster <none> name=redis-master 10.10.10.49 10000
redisslave name=redisslave name=redisslave 10.10.10.109 10001 redisslave name=redisslave name=redisslave 10.10.10.109 10001
frontend <none> name=frontend 10.10.10.149 9998 frontend <none> name=frontend 10.10.10.149 9998
......
...@@ -104,7 +104,6 @@ elasticsearch-logging kubernetes.io/cluster-service=true,name=elasticsearch-l ...@@ -104,7 +104,6 @@ elasticsearch-logging kubernetes.io/cluster-service=true,name=elasticsearch-l
kibana-logging kubernetes.io/cluster-service=true,name=kibana-logging name=kibana-logging 10.0.188.118 5601/TCP kibana-logging kubernetes.io/cluster-service=true,name=kibana-logging name=kibana-logging 10.0.188.118 5601/TCP
kube-dns k8s-app=kube-dns,kubernetes.io/cluster-service=true,name=kube-dns k8s-app=kube-dns 10.0.0.10 53/UDP kube-dns k8s-app=kube-dns,kubernetes.io/cluster-service=true,name=kube-dns k8s-app=kube-dns 10.0.0.10 53/UDP
kubernetes component=apiserver,provider=kubernetes <none> 10.0.0.2 443/TCP kubernetes component=apiserver,provider=kubernetes <none> 10.0.0.2 443/TCP
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.0.0.1 80/TCP
monitoring-grafana kubernetes.io/cluster-service=true,name=grafana name=influxGrafana 10.0.254.202 80/TCP monitoring-grafana kubernetes.io/cluster-service=true,name=grafana name=influxGrafana 10.0.254.202 80/TCP
monitoring-heapster kubernetes.io/cluster-service=true,name=heapster name=heapster 10.0.19.214 80/TCP monitoring-heapster kubernetes.io/cluster-service=true,name=heapster name=heapster 10.0.19.214 80/TCP
monitoring-influxdb name=influxGrafana name=influxGrafana 10.0.198.71 80/TCP monitoring-influxdb name=influxGrafana name=influxGrafana 10.0.198.71 80/TCP
......
...@@ -89,7 +89,6 @@ cluster/kubectl.sh get services ...@@ -89,7 +89,6 @@ cluster/kubectl.sh get services
NAME LABELS SELECTOR IP PORT(S) NAME LABELS SELECTOR IP PORT(S)
frontendservice <none> name=frontendhttp 10.0.0.241 3000/TCP frontendservice <none> name=frontendhttp 10.0.0.241 3000/TCP
kubernetes component=apiserver,provider=kubernetes <none> 10.0.0.2 443/TCP kubernetes component=apiserver,provider=kubernetes <none> 10.0.0.2 443/TCP
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.0.0.1 80/TCP
``` ```
......
...@@ -54,7 +54,6 @@ POD IP CONTAINER(S) IMAGE(S) ...@@ -54,7 +54,6 @@ POD IP CONTAINER(S) IMAGE(S)
spark-master 192.168.90.14 spark-master mattf/spark-master 172.18.145.8/172.18.145.8 name=spark-master Running spark-master 192.168.90.14 spark-master mattf/spark-master 172.18.145.8/172.18.145.8 name=spark-master Running
NAME LABELS SELECTOR IP PORT NAME LABELS SELECTOR IP PORT
kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443 kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.254.0.1 80
spark-master name=spark-master name=spark-master 10.254.125.166 7077 spark-master name=spark-master name=spark-master 10.254.125.166 7077
``` ```
...@@ -135,7 +134,6 @@ spark-worker-controller-5v48c 192.168.90.17 spark-worker mattf/sp ...@@ -135,7 +134,6 @@ spark-worker-controller-5v48c 192.168.90.17 spark-worker mattf/sp
spark-worker-controller-ehq23 192.168.35.17 spark-worker mattf/spark-worker 172.18.145.12/172.18.145.12 name=spark-worker,uses=spark-master Running spark-worker-controller-ehq23 192.168.35.17 spark-worker mattf/spark-worker 172.18.145.12/172.18.145.12 name=spark-worker,uses=spark-master Running
NAME LABELS SELECTOR IP PORT NAME LABELS SELECTOR IP PORT
kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443 kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.254.0.1 80
spark-master name=spark-master name=spark-master 10.254.125.166 7077 spark-master name=spark-master name=spark-master 10.254.125.166 7077
$ sudo docker run -it mattf/spark-base sh $ sudo docker run -it mattf/spark-base sh
......
...@@ -62,7 +62,6 @@ zookeeper 192.168.86.4 zookeeper mattf/zookeeper ...@@ -62,7 +62,6 @@ zookeeper 192.168.86.4 zookeeper mattf/zookeeper
$ kubectl get services $ kubectl get services
NAME LABELS SELECTOR IP PORT NAME LABELS SELECTOR IP PORT
kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443 kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.254.0.1 80
zookeeper name=zookeeper name=zookeeper 10.254.139.141 2181 zookeeper name=zookeeper name=zookeeper 10.254.139.141 2181
$ echo ruok | nc 10.254.139.141 2181; echo $ echo ruok | nc 10.254.139.141 2181; echo
...@@ -97,7 +96,6 @@ Ensure that the Nimbus service is running and functional. ...@@ -97,7 +96,6 @@ Ensure that the Nimbus service is running and functional.
$ kubectl get services $ kubectl get services
NAME LABELS SELECTOR IP PORT NAME LABELS SELECTOR IP PORT
kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443 kubernetes component=apiserver,provider=kubernetes <none> 10.254.0.2 443
kubernetes-ro component=apiserver,provider=kubernetes <none> 10.254.0.1 80
zookeeper name=zookeeper name=zookeeper 10.254.139.141 2181 zookeeper name=zookeeper name=zookeeper 10.254.139.141 2181
nimbus name=nimbus name=nimbus 10.254.115.208 6627 nimbus name=nimbus name=nimbus 10.254.115.208 6627
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment