whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correcting minikube quickstart steps (#14355)

Browse Source 
* 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 <franklinyu@hotmail.com>

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

Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>

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

Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>

* Corrected formatting 

Corrected formatting

* Correcting number sequence 

Correcting number sequence
This commit is contained in:
Rajesh Deshpande
2019-05-20 17:57:16 +05:30
committed by Kubernetes Prow Robot
parent a7e4e00d51
commit d135d566b1
1 changed files with 108 additions and 81 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/minikube.md
+108 -81
View File
@@ -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) * 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) * 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 1. Start a minikube
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 minikube start
``` ```
``` The output shows that the kubernetes cluster is started:
service/hello-minikube exposed
``` ```
Starting local Kubernetes cluster...
Running pre-create checks...
Creating machine...
Starting local Kubernetes cluster...
```
2. Create an echo server deployment
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. kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
To check whether the pod is up and running we can use the following: ```
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 get pod kubectl expose deployment hello-minikube --type=NodePort
``` ```
``` The output of a successful command verifies that the service is created:
NAME READY STATUS RESTARTS AGE
hello-minikube-3383150820-vctvh 0/1 ContainerCreating 0 3s ```
``` service/hello-minikube exposed
```
We can see that the pod is still being created from the ContainerCreating status 4. Check whether the pod is up and running
kubectl get pod
``` ```
NAME READY STATUS RESTARTS AGE kubectl get pod
hello-minikube-3383150820-vctvh 1/1 Running 0 13s ```
``` The output displays the pod is still being created:
```
NAME READY STATUS RESTARTS AGE
hello-minikube-3383150820-vctvh 0/1 ContainerCreating 0 3s
```
We can see that the pod is now Running and we will now be able to curl it: 5. Wait for while and then check again, whether the pod is up and running using same command
``` ```
curl $(minikube service hello-minikube --url) 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
```
Hostname: hello-minikube-7c77b68cff-8wdzq 6. Curl service which we have created
Pod Information: ```
-no pod information available- curl $(minikube service hello-minikube --url)
```
Output looks similer to this:
```
Hostname: hello-minikube-7c77b68cff-8wdzq
Server values: Pod Information:
server_version=nginx: 1.13.3 - lua: 10008 -no pod information available-
Request Information: Server values:
client_address=172.17.0.1 server_version=nginx: 1.13.3 - lua: 10008
method=GET
real path=/
query=
request_version=1.1
request_scheme=http
request_uri=http://192.168.99.100:8080/
Request Headers: Request Information:
accept=*/* client_address=172.17.0.1
host=192.168.99.100:30674 method=GET
user-agent=curl/7.47.0 real path=/
query=
request_version=1.1
request_scheme=http
request_uri=http://192.168.99.100:8080/
Request Body: Request Headers:
-no body in request- accept=*/*
``` host=192.168.99.100:30674
user-agent=curl/7.47.0
```shell Request Body:
kubectl delete services hello-minikube -no body in request-
``` ```
``` 7. Delete the service which we have created
service "hello-minikube" deleted
```
```shell ```
kubectl delete deployment hello-minikube kubectl delete services hello-minikube
``` ```
``` The output of a successful command verifies that the service is deleted:
deployment.extensions "hello-minikube" deleted
``` ```
service "hello-minikube" deleted
```
8. Delete the deployment which we have created
```shell ```
minikube stop kubectl delete deployment hello-minikube
``` ```
``` The output of a successful command verifies that the deployment is deleted:
Stopping local Kubernetes cluster...
Stopping "minikube"... ```
``` 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 ### Alternative Container Runtimes