From c848bf0487da82d80e63e5d5a5f7c3ee6c5650b2 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Tue, 4 Oct 2016 11:55:33 +0100 Subject: [PATCH] Demo app is now in different namespace Change instructions to show use of 'sock-shop' namespace rather than default. --- docs/getting-started-guides/kubeadm.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/getting-started-guides/kubeadm.md b/docs/getting-started-guides/kubeadm.md index 6852438004..86de0652c2 100644 --- a/docs/getting-started-guides/kubeadm.md +++ b/docs/getting-started-guides/kubeadm.md @@ -182,9 +182,9 @@ To learn more about the sample microservices app, see the [GitHub README](https: You can then find out the port that the [NodePort feature of services](/docs/user-guide/services/) allocated for the front-end service by running: - # kubectl describe svc front-end + # kubectl describe svc front-end -n sock-shop Name: front-end - Namespace: default + Namespace: sock-shop Labels: name=front-end Selector: name=front-end Type: NodePort @@ -194,7 +194,7 @@ You can then find out the port that the [NodePort feature of services](/docs/use Endpoints: Session Affinity: None -It takes several minutes to download and start all the containers, watch the output of `kubectl get pods` to see when they're all up and running. +It takes several minutes to download and start all the containers, watch the output of `kubectl get pods -n sock-shop` to see when they're all up and running. Then go to the IP address of your cluster's master node in your browser, and specify the given port. So for example, `http://:`.