You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 18, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ Ensure your kubernetes cluster is reachable by running the `kubectl` command.
71
71
```bash
72
72
$ kubectl get nodes
73
73
NAME STATUS AGE VERSION
74
-
x.x.x.x Ready 17h v1.5.3-2+be7137fd3ad68f
74
+
x.x.x.x Ready 17h v1.5.3-2+be7137fd3ad68f
75
75
```
76
76
77
77
> Note: If this step fails see troubleshooting docs at [Minikube](https://kubernetes.io/docs/getting-started-guides/minikube) or [IBM Bluemix Container Service](https://console.ng.bluemix.net/docs/containers/cs_troubleshoot.html#cs_troubleshoot).
@@ -152,9 +152,10 @@ After you have created all the services and deployments, wait for 3 to 5 minutes
152
152
After few minutes run the following commands to get your public IP and NodePort number.
153
153
154
154
```bash
155
-
$ kubectl get nodes
156
-
NAME STATUS AGE
157
-
169.47.241.22 Ready 23h
155
+
$ $ bx cs workers <cluster_name>
156
+
OK
157
+
ID Public IP Private IP Machine Type State Status
158
+
kube-hou02-pa817264f1244245d38c4de72fffd527ca-w1 169.47.241.22 10.10.10.148 free normal Ready
0 commit comments