Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update minikube.md #13803

Merged
merged 1 commit into from
Apr 25, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 11 additions & 7 deletions content/en/docs/setup/minikube.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,26 +68,30 @@ kubectl expose deployment hello-minikube --type=NodePort
```
service/hello-minikube exposed
```

We have now launched an echoserver pod but we have to wait until the pod is up before curling/accessing it
via the exposed service.
To check whether the pod is up and running we can use the following:

```
# We have now launched an echoserver pod but we have to wait until the pod is up before curling/accessing it
# via the exposed service.
# To check whether the pod is up and running we can use the following:
kubectl get pod
```
```
NAME READY STATUS RESTARTS AGE
hello-minikube-3383150820-vctvh 0/1 ContainerCreating 0 3s
```
```
# We can see that the pod is still being created from the ContainerCreating status

We can see that the pod is still being created from the ContainerCreating status
kubectl get pod
```

```
NAME READY STATUS RESTARTS AGE
hello-minikube-3383150820-vctvh 1/1 Running 0 13s
```

We can see that the pod is now Running and we will now be able to curl it:

```
# We can see that the pod is now Running and we will now be able to curl it:
curl $(minikube service hello-minikube --url)
```
```
Expand Down