Skip to content

Commit

Permalink
Correcting minikube quickstart steps (#14355)
Browse files Browse the repository at this point in the history 
* Correcting minikube quickstart steps

In minikube quickstart section , it was difficult to differentiate between command and its output. Also, There was no details given for each steps and its expected output. This PR fixes these issues.

* Correcting number formatting

Correcting number formatting

* Correcting numbering

Correcting numbering

* Update content/en/docs/setup/minikube.md

Co-Authored-By: Franklin Yu <[email protected]>

* Update content/en/docs/setup/minikube.md

Co-Authored-By: Franklin Yu <[email protected]>

* Update content/en/docs/setup/minikube.md

Co-Authored-By: Franklin Yu <[email protected]>

* Corrected formatting 

Corrected formatting

* Correcting number sequence 

Correcting number sequence
  • Loading branch information
@rajeshdeshpande02 @k8s-ci-robot
rajeshdeshpande02 authored and k8s-ci-robot committed May 20, 2019
1 parent a7e4e00 commit d135d56
Showing 1 changed file with 124 additions and 97 deletions.
221 changes: 124 additions & 97 deletions content/en/docs/setup/minikube.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -45,103 +45,130 @@ Note that the IP below is dynamic and can change. It can be retrieved with `mini
* vmware ([driver installation](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#vmware-unified-driver)) (VMware unified driver)
* none (Runs the Kubernetes components on the host and not in a VM. Using this driver requires Docker ([docker install](https://docs.docker.com/install/linux/docker-ce/ubuntu/)) and a Linux environment)

```shell
minikube start
```
```
Starting local Kubernetes cluster...
Running pre-create checks...
Creating machine...
Starting local Kubernetes cluster...
```
```shell
kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
```
```
deployment.apps/hello-minikube created
```

```shell
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:

```
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
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:

```
curl $(minikube service hello-minikube --url)
```
```
Hostname: hello-minikube-7c77b68cff-8wdzq
Pod Information:
-no pod information available-
Server values:
server_version=nginx: 1.13.3 - lua: 10008
Request Information:
client_address=172.17.0.1
method=GET
real path=/
query=
request_version=1.1
request_scheme=http
request_uri=http://192.168.99.100:8080/
Request Headers:
accept=*/*
host=192.168.99.100:30674
user-agent=curl/7.47.0
Request Body:
-no body in request-
```

```shell
kubectl delete services hello-minikube
```
```
service "hello-minikube" deleted
```

```shell
kubectl delete deployment hello-minikube
```
```
deployment.extensions "hello-minikube" deleted
```

```shell
minikube stop
```
```
Stopping local Kubernetes cluster...
Stopping "minikube"...
```
1. Start a minikube

```
minikube start
```
The output shows that the kubernetes cluster is started:
```
Starting local Kubernetes cluster...
Running pre-create checks...
Creating machine...
Starting local Kubernetes cluster...
```
2. Create an echo server deployment
```
kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
```
The output of a successful command verifies that the deployment is created:
```
deployment.apps/hello-minikube created
```
3. Expose an echo server deployment to create service
```
kubectl expose deployment hello-minikube --type=NodePort
```
The output of a successful command verifies that the service is created:
```
service/hello-minikube exposed
```
4. Check whether the pod is up and running
```
kubectl get pod
```
The output displays the pod is still being created:
```
NAME READY STATUS RESTARTS AGE
hello-minikube-3383150820-vctvh 0/1 ContainerCreating 0 3s
```
5. Wait for while and then check again, whether the pod is up and running using same command
```
kubectl get pod
```
Now the output displays the pod is created and it is running:
```
NAME READY STATUS RESTARTS AGE
hello-minikube-3383150820-vctvh 1/1 Running 0 13s
```
6. Curl service which we have created
```
curl $(minikube service hello-minikube --url)
```
Output looks similer to this:
```
Hostname: hello-minikube-7c77b68cff-8wdzq
Pod Information:
-no pod information available-
Server values:
server_version=nginx: 1.13.3 - lua: 10008
Request Information:
client_address=172.17.0.1
method=GET
real path=/
query=
request_version=1.1
request_scheme=http
request_uri=http://192.168.99.100:8080/
Request Headers:
accept=*/*
host=192.168.99.100:30674
user-agent=curl/7.47.0
Request Body:
-no body in request-
```
7. Delete the service which we have created
```
kubectl delete services hello-minikube
```
The output of a successful command verifies that the service is deleted:
```
service "hello-minikube" deleted
```
8. Delete the deployment which we have created
```
kubectl delete deployment hello-minikube
```
The output of a successful command verifies that the deployment is deleted:
```
deployment.extensions "hello-minikube" deleted
```
9. Stop a minikube
```
minikube stop
```
The output displays the kubernetes cluster is stopping:

```
Stopping local Kubernetes cluster...
Stopping "minikube"...
```

### Alternative Container Runtimes

Expand Down

0 comments on commit d135d56

Please sign in to comment.