Minion->Node rename: docs/ machine names only, except gce/aws
This commit is contained in:
@@ -181,9 +181,9 @@ $ virsh -c qemu:///system list
|
||||
Id Name State
|
||||
----------------------------------------------------
|
||||
15 kubernetes_master running
|
||||
16 kubernetes_minion-01 running
|
||||
17 kubernetes_minion-02 running
|
||||
18 kubernetes_minion-03 running
|
||||
16 kubernetes_node-01 running
|
||||
17 kubernetes_node-02 running
|
||||
18 kubernetes_node-03 running
|
||||
```
|
||||
|
||||
You can check that the Kubernetes cluster is working with:
|
||||
@@ -208,7 +208,7 @@ Connect to `kubernetes_master`:
|
||||
ssh core@192.168.10.1
|
||||
```
|
||||
|
||||
Connect to `kubernetes_minion-01`:
|
||||
Connect to `kubernetes_node-01`:
|
||||
|
||||
```sh
|
||||
ssh core@192.168.10.2
|
||||
|
@@ -77,10 +77,10 @@ $ kubectl get pods --namespace=kube-system
|
||||
NAME READY REASON RESTARTS AGE
|
||||
elasticsearch-logging-v1-78nog 1/1 Running 0 2h
|
||||
elasticsearch-logging-v1-nj2nb 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-minion-5oq0 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-minion-6896 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-minion-l1ds 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-minion-lz9j 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-node-5oq0 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-node-6896 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-node-l1ds 1/1 Running 0 2h
|
||||
fluentd-elasticsearch-kubernetes-node-lz9j 1/1 Running 0 2h
|
||||
kibana-logging-v1-bhpo8 1/1 Running 0 2h
|
||||
kube-dns-v3-7r1l9 3/3 Running 0 2h
|
||||
monitoring-heapster-v4-yl332 1/1 Running 1 2h
|
||||
|
@@ -41,10 +41,10 @@ logging and DNS resolution for names of Kubernetes services:
|
||||
```console
|
||||
$ kubectl get pods --namespace=kube-system
|
||||
NAME READY REASON RESTARTS AGE
|
||||
fluentd-cloud-logging-kubernetes-minion-0f64 1/1 Running 0 32m
|
||||
fluentd-cloud-logging-kubernetes-minion-27gf 1/1 Running 0 32m
|
||||
fluentd-cloud-logging-kubernetes-minion-pk22 1/1 Running 0 31m
|
||||
fluentd-cloud-logging-kubernetes-minion-20ej 1/1 Running 0 31m
|
||||
fluentd-cloud-logging-kubernetes-node-0f64 1/1 Running 0 32m
|
||||
fluentd-cloud-logging-kubernetes-node-27gf 1/1 Running 0 32m
|
||||
fluentd-cloud-logging-kubernetes-node-pk22 1/1 Running 0 31m
|
||||
fluentd-cloud-logging-kubernetes-node-20ej 1/1 Running 0 31m
|
||||
kube-dns-v3-pk22 3/3 Running 0 32m
|
||||
monitoring-heapster-v1-20ej 0/1 Running 9 32m
|
||||
```
|
||||
@@ -215,7 +215,7 @@ Note the first container counted to 108 and then it was terminated. When the nex
|
||||
|
||||
```console
|
||||
SELECT metadata.timestamp, structPayload.log
|
||||
FROM [mylogs.kubernetes_counter_default_count_20150611]
|
||||
FROM [mylogs.kubernetes_counter_default_count_20150611]
|
||||
ORDER BY metadata.timestamp DESC
|
||||
```
|
||||
|
||||
|
Reference in New Issue
Block a user