Fix numbered lists (#10887)

* Fix numbered lists

* Update hello-minikube.md

* Update hello-minikube.md

* Update hello-minikube.md

* Update hello-minikube.md

* Update hello-minikube.md

* Update hello-minikube.md

* Update hello-minikube.md

* remove redundant note labels
This commit is contained in:
Cody Clark 2018-11-08 11:13:04 -08:00 committed by k8s-ci-robot
parent c34ef23f3c
commit e74e9394cd
1 changed files with 108 additions and 120 deletions

View File

@ -48,21 +48,15 @@ For more information, read the Docker documentation for [docker build](https://d
1. Click **Launch Terminal** 1. Click **Launch Terminal**
{{< kat-button >}} {{< kat-button >}}
{{< note >}} {{< note >}}If you installed Minikube locally, run `minikube start`.{{< /note >}}
If you installed Minikube locally, run
```shell
minikube start
```
{{< /note >}}
2. Open the Kubernetes dashboard in a browser: 2. Open the Kubernetes dashboard in a browser:
```shell ```shell
minikube dashboard minikube dashboard
``` ```
3. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then click **Select port to view on Host 1**. 3. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then click **Select port to view on Host 1**.
@ -80,51 +74,48 @@ recommended way to manage the creation and scaling of Pods.
1. Use the `kubectl run` command to create a Deployment that manages a Pod. The 1. Use the `kubectl run` command to create a Deployment that manages a Pod. The
Pod runs a Container based on the provided Docker image. Pod runs a Container based on the provided Docker image.
```shell ```shell
kubectl run hello-node --image=gcr.io/hello-minikube-zero-install/hello-node --port=8080 kubectl run hello-node --image=gcr.io/hello-minikube-zero-install/hello-node --port=8080
``` ```
2. View the Deployment: 2. View the Deployment:
```shell ```shell
kubectl get deployments kubectl get deployments
``` ```
Output: Output:
```shell ```shell
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
hello-node 1 1 1 1 1m hello-node 1 1 1 1 1m
``` ```
3. View the Pod: 3. View the Pod:
```shell ```shell
kubectl get pods kubectl get pods
``` ```
Output: Output:
```shell ```shell
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
hello-node-5f76cf6ccf-br9b5 1/1 Running 0 1m hello-node-5f76cf6ccf-br9b5 1/1 Running 0 1m
``` ```
4. View cluster events: 4. View cluster events:
```shell ```shell
kubectl get events kubectl get events
``` ```
5. View the `kubectl` configuration: 5. View the `kubectl` configuration:
```shell ```shell
kubectl config view kubectl config view
``` ```
{{< note >}} {{< note >}}For more information about `kubectl`commands, see the [kubectl overview](/docs/user-guide/kubectl-overview/).{{< /note >}}
For more information about `kubectl`commands, see the
[kubectl overview](/docs/user-guide/kubectl-overview/).
{{< /note >}}
## Create a Service ## Create a Service
@ -135,41 +126,41 @@ Kubernetes [*Service*](/docs/concepts/services-networking/service/).
1. Expose the Pod to the public internet using the `kubectl expose` command: 1. Expose the Pod to the public internet using the `kubectl expose` command:
```shell ```shell
kubectl expose deployment hello-node --type=LoadBalancer kubectl expose deployment hello-node --type=LoadBalancer
``` ```
2. View the Service you just created: 2. View the Service you just created:
```shell ```shell
kubectl get services kubectl get services
``` ```
Output: Output:
```shell ```shell
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
hello-node LoadBalancer 10.108.144.78 <pending> 8080:30369/TCP 21s hello-node LoadBalancer 10.108.144.78 <pending> 8080:30369/TCP 21s
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 23m kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 23m
``` ```
The `--type=LoadBalancer` flag indicates that you want to expose your Service The `--type=LoadBalancer` flag indicates that you want to expose your Service
outside of the cluster. On cloud providers that support load balancers, outside of the cluster. On cloud providers that support load balancers,
an external IP address would be provisioned to access the Service. On Minikube, an external IP address would be provisioned to access the Service. On Minikube,
the `LoadBalancer` type makes the Service accessible through the `minikube service` the `LoadBalancer` type makes the Service accessible through the `minikube service`
command. command.
3. Run the following command: 3. Run the following command:
```shell ```shell
minikube service hello-node minikube service hello-node
``` ```
4. Katacoda environment only: Click the plus sign, then click **Select port to view on Host 1**. 4. Katacoda environment only: Click the plus sign, and then click **Select port to view on Host 1**.
5. Katacoda environment only: Type in the Port number following `8080:`, and then click **Display Port**. 5. Katacoda environment only: Type in the Port number following `8080:`, and then click **Display Port**.
This opens up a browser window that serves your app and shows the "Hello World" message. This opens up a browser window that serves your app and shows the "Hello World" message.
## Enable addons ## Enable addons
@ -177,81 +168,78 @@ Minikube has a set of built-in addons that can be enabled, disabled and opened i
1. List the currently supported addons: 1. List the currently supported addons:
```shell ```shell
minikube addons list minikube addons list
``` ```
Output: Output:
```shell ```shell
- addon-manager: enabled addon-manager: enabled
- coredns: disabled coredns: disabled
- dashboard: enabled dashboard: enabled
- default-storageclass: enabled default-storageclass: enabled
- efk: disabled efk: disabled
- freshpod: disabled freshpod: disabled
- heapster: disabled heapster: disabled
- ingress: disabled ingress: disabled
- kube-dns: enabled kube-dns: enabled
- metrics-server: disabled metrics-server: disabled
- nvidia-driver-installer: disabled nvidia-driver-installer: disabled
- nvidia-gpu-device-plugin: disabled nvidia-gpu-device-plugin: disabled
- registry: disabled registry: disabled
- registry-creds: disabled registry-creds: disabled
- storage-provisioner: enabled storage-provisioner: enabled
``` ```
{{< note >}}
Minikube must be running for these commands to take effect.
{{< /note >}}
2. Enable an addon, for example, `heapster`: 2. Enable an addon, for example, `heapster`:
```shell ```shell
minikube addons enable heapster minikube addons enable heapster
``` ```
Output: Output:
```shell ```shell
heapster was successfully enabled heapster was successfully enabled
``` ```
3. View the Pod and Service you just created: 3. View the Pod and Service you just created:
```shell ```shell
kubectl get po,svc -n kube-system kubectl get pod,svc -n kube-system
``` ```
Output: Output:
```shell ```shell
NAME READY STATUS RESTARTS AGE NAME READY STATUS RESTARTS AGE
pod/heapster-9jttx 1/1 Running 0 26s pod/heapster-9jttx 1/1 Running 0 26s
pod/influxdb-grafana-b29w8 2/2 Running 0 26s pod/influxdb-grafana-b29w8 2/2 Running 0 26s
pod/kube-addon-manager-minikube 1/1 Running 0 34m pod/kube-addon-manager-minikube 1/1 Running 0 34m
pod/kube-dns-6dcb57bcc8-gv7mw 3/3 Running 0 34m pod/kube-dns-6dcb57bcc8-gv7mw 3/3 Running 0 34m
pod/kubernetes-dashboard-5498ccf677-cgspw 1/1 Running 0 34m pod/kubernetes-dashboard-5498ccf677-cgspw 1/1 Running 0 34m
pod/storage-provisioner 1/1 Running 0 34m pod/storage-provisioner 1/1 Running 0 34m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/heapster ClusterIP 10.96.241.45 <none> 80/TCP 26s service/heapster ClusterIP 10.96.241.45 <none> 80/TCP 26s
service/kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP 34m service/kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP 34m
service/kubernetes-dashboard NodePort 10.109.29.1 <none> 80:30000/TCP 34m service/kubernetes-dashboard NodePort 10.109.29.1 <none> 80:30000/TCP 34m
service/monitoring-grafana NodePort 10.99.24.54 <none> 80:30002/TCP 26s service/monitoring-grafana NodePort 10.99.24.54 <none> 80:30002/TCP 26s
service/monitoring-influxdb ClusterIP 10.111.169.94 <none> 8083/TCP,8086/TCP 26s service/monitoring-influxdb ClusterIP 10.111.169.94 <none> 8083/TCP,8086/TCP 26s
``` ```
4. Disable `heapster`: 4. Disable `heapster`:
```shell ```shell
minikube addons disable heapster minikube addons disable heapster
``` ```
Output: Output:
```shell ```shell
heapster was successfully disabled heapster was successfully disabled
``` ```
## Clean up ## Clean up