From 10fb247357b1f8efec2a76c5f08aedbecdb88116 Mon Sep 17 00:00:00 2001
From: attardi <giuseppe.attardi@garr.it>
Date: Thu, 11 Jan 2018 03:12:09 +0100
Subject: [PATCH] Edited.
---
README.md | 16 ++++------------
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/README.md b/README.md
index 17a4f6e..070eac0 100644
--- a/README.md
+++ b/README.md
@@ -190,8 +190,9 @@ enabled or disabled by setting the `enable-dashboard-addons` config on the
$ juju config kubernetes-master enable-dashboard-addons=true
```
-To access the dashboard, you may establish a secure tunnel to your cluster with
-the following command:
+To access the dashboard, you may establish a secure tunnel to your
+cluster through the `kubernetes-master` node, with the following
+command:
```
$ juju ssh kubernetes-master/N
@@ -328,12 +329,7 @@ which binds an 'endpoint', using all 3 of the 'microbots' pods.
[xip.io](https://xip.io) domain to simulate a proper DNS service.
-#### Running the packaged example
-
-Run a Juju action to create the example microbot web application:
-
- $ juju run-action kubernetes-worker/N microbot replicas=3
- Action queued with id: db7cc72b-5f35-4a4d-877c-284c4b776eb8
+Wait for the action to comlpete:
$ juju show-action-output db7cc72b-5f35-4a4d-877c-284c4b776eb8
results:
@@ -350,10 +346,6 @@ Run a Juju action to create the example microbot web application:
At this point, you can inspect the cluster to observe the workload coming
online.
-```
-$ juju ssh kubernetes-worker/N
-```
-
#### List the pods
$ kubectl get pods
--
GitLab