From d12a9b55acc68ae8644de7c0153197f8bfdf8a98 Mon Sep 17 00:00:00 2001 From: Kelsey Hightower Date: Fri, 8 Jul 2016 17:36:55 -0700 Subject: [PATCH] clean up docs --- docs/05-kubernetes-worker.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/05-kubernetes-worker.md b/docs/05-kubernetes-worker.md index 0d963d2..83a1793 100644 --- a/docs/05-kubernetes-worker.md +++ b/docs/05-kubernetes-worker.md @@ -3,12 +3,16 @@ In this lab you will bootstrap 3 Kubernetes worker nodes. The following virtual machines will be used: ``` -NAME ZONE MACHINE_TYPE INTERNAL_IP STATUS -worker0 us-central1-f n1-standard-1 10.240.0.30 RUNNING -worker1 us-central1-f n1-standard-1 10.240.0.31 RUNNING -worker2 us-central1-f n1-standard-1 10.240.0.32 RUNNING +gcloud compute instances list ``` +```` +NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS +worker0 us-central1-f n1-standard-1 10.240.0.30 XXX.XXX.XXX.XXX RUNNING +worker1 us-central1-f n1-standard-1 10.240.0.31 XXX.XXX.XXX.XXX RUNNING +worker2 us-central1-f n1-standard-1 10.240.0.32 XXX.XXX.XXX.XXX RUNNING +```` + ## Why Kubernetes worker nodes are responsible for running your containers. All Kubernetes clusters need one or more worker nodes. We are running the worker nodes on dedicated machines for the following reasons: