---
title: 你好，Minikube
content_type: tutorial
weight: 5
menu:
  main:
    title: "Get Started"
    weight: 10
    post: >
      <p>准备好动手操作了么？构建一个简单的 Kubernetes 集群来运行示例应用。</p>
card:
  name: tutorials
  weight: 10
---
<!--
title: Hello Minikube
content_type: tutorial
weight: 5
menu:
  main:
    title: "Get Started"
    weight: 10
    post: >
      <p>Ready to get your hands dirty? Build a simple Kubernetes cluster that runs a sample app.</p>
card:
  name: tutorials
  weight: 10
-->

<!-- overview -->

<!--
This tutorial shows you how to run a sample app
on Kubernetes using minikube and Katacoda.
Katacoda provides a free, in-browser Kubernetes environment.
-->
本教程向你展示如何使用 Minikube 和 Katacoda
在 Kubernetes 上运行一个应用示例。Katacoda 提供免费的浏览器内 Kubernetes 环境。

<!--
{{< note >}}
You can also follow this tutorial if you've installed minikube locally.
See [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions.
{{< /note >}}
-->
{{< note >}}
如果你已在本地安装 Minikube，也可以按照本教程操作。
安装指南参阅 [minikube start](https://minikube.sigs.k8s.io/docs/start/) 。
{{< /note >}}


## {{% heading "objectives" %}}

<!--
* Deploy a sample application to minikube.
* Run the app.
* View application logs.
-->
* 将一个示例应用部署到 Minikube。
* 运行应用程序。
* 查看应用日志

## {{% heading "prerequisites" %}}


<!--
This tutorial provides a container image that uses NGINX to echo back all the requests.
-->
本教程提供了容器镜像，使用 NGINX 来对所有请求做出回应：

<!-- lessoncontent -->

<!--
## Create a minikube cluster

1. Click **Launch Terminal**
-->
## 创建 Minikube 集群

1. 点击 **启动终端**

   {{< kat-button >}}

   <!-- 
   If you installed minikube locally, run `minikube start`. Before you run `minikube dashboard`, you should open a new terminal, start `minikube dashboard` there, and then switch back to the main terminal.
   -->
   {{< note >}}
   如果你在本地安装了 Minikube，运行 `minikube start`。
   在运行 `minikube dashboard` 之前，你应该打开一个新终端，
   在此启动 `minikube dashboard` ，然后切换回主终端。 
   {{< /note >}}

<!--
2. Open the Kubernetes dashboard in a browser:
-->
2. 在浏览器中打开 Kubernetes 仪表板（Dashboard）：

   ```shell
   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 环境：在终端窗口的顶部，单击加号，然后单击 **选择要在主机 1 上查看的端口**。

<!--
4. Katacoda environment only: Type `30000`, and then click **Display Port**.
-->
4. 仅限 Katacoda 环境：输入“30000”，然后单击 **显示端口**。

<!--
The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. 
You can create Kubernetes resources on the dashboard such as Deployment and Service.

If you are running in an environment as root, see [Open Dashboard with URL](#open-dashboard-with-url).

By default, the dashboard is only accessible from within the internal Kubernetes virtual network.
The `dashboard` command creates a temporary proxy to make the dashboard accessible from outside the Kubernetes virtual network.

To stop the proxy, run `Ctrl+C` to exit the process.
After the command exits, the dashboard remains running in the Kubernetes cluster.
You can run the `dashboard` command again to create another proxy to access the dashboard.
-->
{{< note >}}
`dashboard` 命令启用仪表板插件，并在默认的 Web 浏览器中打开代理。
你可以在仪表板上创建 Kubernetes 资源，例如 Deployment 和 Service。

如果你以 root 用户身份在环境中运行，
请参见[使用 URL 打开仪表板](#open-dashboard-with-url)。

默认情况下，仪表板只能从内部 Kubernetes 虚拟网络中访问。
`dashboard` 命令创建一个临时代理，使仪表板可以从 Kubernetes 虚拟网络外部访问。

要停止代理，请运行 `Ctrl+C` 退出该进程。仪表板仍在运行中。
命令退出后，仪表板仍然在 Kubernetes 集群中运行。
你可以再次运行 `dashboard` 命令创建另一个代理来访问仪表板。

{{< /note >}}

<!--
## Open Dashboard with URL
-->
## 使用 URL 打开仪表板

<!--
If you don't want to open a web browser, run the dashboard command with the `--url` flag to emit a URL:
-->
如果你不想打开 Web 浏览器，请使用 `--url` 标志运行显示板命令以得到 URL：

```shell
minikube dashboard --url
```

<!--

## Create a Deployment

A Kubernetes [*Pod*](/docs/concepts/workloads/pods/) is a group of one or more Containers,
tied together for the purposes of administration and networking. The Pod in this
tutorial has only one Container. A Kubernetes
[*Deployment*](/docs/concepts/workloads/controllers/deployment/) checks on the health of your
Pod and restarts the Pod's Container if it terminates. Deployments are the
recommended way to manage the creation and scaling of Pods.
-->

## 创建 Deployment

Kubernetes [*Pod*](/zh/docs/concepts/workloads/pods/) 是由一个或多个
为了管理和联网而绑定在一起的容器构成的组。 本教程中的 Pod 只有一个容器。
Kubernetes [*Deployment*](/zh/docs/concepts/workloads/controllers/deployment/)
检查 Pod 的健康状况，并在 Pod 中的容器终止的情况下重新启动新的容器。
Deployment 是管理 Pod 创建和扩展的推荐方法。

<!--
1. Use the `kubectl create` command to create a Deployment that manages a Pod. The
Pod runs a Container based on the provided Docker image.
-->
1. 使用 `kubectl create` 命令创建管理 Pod 的 Deployment。该 Pod 根据提供的 Docker
   镜像运行 Container。

   ```shell
   kubectl create deployment hello-node --image=k8s.gcr.io/echoserver:1.4
   ```

<!--
2. View the Deployment:
-->

2. 查看 Deployment：

   ```shell
   kubectl get deployments
   ```

   <!--
   The output is similar to:
   -->

   输出结果类似于这样：

   ```
   NAME         READY   UP-TO-DATE   AVAILABLE   AGE
   hello-node   1/1     1            1           1m
   ```

<!--
3. View the Pod:
-->
3. 查看 Pod：

   ```shell
   kubectl get pods
   ```

   <!--
   The output is similar to:
   -->

   输出结果类似于这样：

   ```
   NAME                          READY     STATUS    RESTARTS   AGE
   hello-node-5f76cf6ccf-br9b5   1/1       Running   0          1m
   ```

<!--
4. View cluster events:
-->
4. 查看集群事件：

   ```shell
   kubectl get events
   ```

<!--
5. View the `kubectl` configuration:
-->
5. 查看 `kubectl` 配置：

   ```shell
   kubectl config view
   ```

<!--
For more information about `kubectl`commands, see the
[kubectl overview](/docs/reference/kubectl/).
-->
{{< note >}}
有关 `kubectl` 命令的更多信息，请参阅 [kubectl 概述](/zh/docs/reference/kubectl/)。
{{< /note >}}

<!--
## Create a Service

By default, the Pod is only accessible by its internal IP address within the
Kubernetes cluster. To make the `hello-node` Container accessible from outside the
Kubernetes virtual network, you have to expose the Pod as a
Kubernetes [*Service*](/docs/concepts/services-networking/service/).
-->
## 创建 Service

默认情况下，Pod 只能通过 Kubernetes 集群中的内部 IP 地址访问。
要使得 `hello-node` 容器可以从 Kubernetes 虚拟网络的外部访问，你必须将 Pod
暴露为 Kubernetes [*Service*](/zh/docs/concepts/services-networking/service/)。

<!--
1. Expose the Pod to the public internet using the `kubectl expose` command:
-->
1. 使用 `kubectl expose` 命令将 Pod 暴露给公网：

   ```shell
   kubectl expose deployment hello-node --type=LoadBalancer --port=8080
   ```

   <!--
    The `--type=LoadBalancer` flag indicates that you want to expose your Service
    outside of the cluster.

    The application code inside the image `k8s.gcr.io/echoserver` only listens on TCP port 8080. If you used
    `kubectl expose` to expose a different port, clients could not connect to that other port.
   -->
   这里的 `--type=LoadBalancer` 参数表明你希望将你的 Service 暴露到集群外部。

   镜像 `k8s.gcr.io/echoserver` 中的应用程序代码仅监听 TCP 8080 端口。
   如果你用 `kubectl expose` 暴露了其它的端口，客户端将不能访问其它端口。

<!--
2. View the Service you created:
-->
2. 查看你创建的 Service：

   ```shell
   kubectl get services
   ```

   <!--
   The output is similar to:
   -->

   输出结果类似于这样:

   ```
   NAME         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
   hello-node   LoadBalancer   10.108.144.78   <pending>     8080:30369/TCP   21s
   kubernetes   ClusterIP      10.96.0.1       <none>        443/TCP          23m
   ```

   <!--
   On cloud providers that support load balancers,
   an external IP address would be provisioned to access the Service. On minikube,
   the `LoadBalancer` type makes the Service accessible through the `minikube service`
   command.
   -->
   对于支持负载均衡器的云服务平台而言，平台将提供一个外部 IP 来访问该服务。
   在 Minikube 上，`LoadBalancer` 使得服务可以通过命令 `minikube service` 访问。

<!--
3. Run the following command:
-->
3. 运行下面的命令：

   ```shell
   minikube service hello-node
   ```

<!--
4. Katacoda environment only: Click the plus sign, and then click **Select port to view on Host 1**.
-->
4. 仅限 Katacoda 环境：单击加号，然后单击 **选择要在主机 1 上查看的端口**。

<!--
5. Katacoda environment only: Note the 5-digit port number displayed opposite to `8080` in services output. This port number is randomly generated and it can be different for you. Type your number in the port number text box, then click Display Port. Using the example from earlier, you would type `30369`.

    This opens up a browser window that serves your app and shows the app's response.
-->
5. 仅限 Katacoda 环境：请注意在 service 输出中与 `8080` 对应的长度为 5 位的端口号。
   此端口号是随机生成的，可能与你的不同。
   在端口号文本框中输入你自己的端口号，然后单击显示端口。
   对应于上面的例子，需要输入 `30369`。

   这将打开一个浏览器窗口，为你的应用程序提供服务并显示应用的响应。

<!--
## Enable addons

The minikube tool includes a set of built-in {{< glossary_tooltip text="addons" term_id="addons" >}} that can be enabled, disabled and opened in the local Kubernetes environment.

1. List the currently supported addons:
-->
## 启用插件

Minikube 有一组内置的 {{< glossary_tooltip text="插件" term_id="addons" >}}，
可以在本地 Kubernetes 环境中启用、禁用和打开。

1. 列出当前支持的插件：

   ```shell
   minikube addons list
   ```

   <!--
   The output is similar to:
   -->
   输出结果类似于这样：

   ```
   addon-manager: enabled
   dashboard: enabled
   default-storageclass: enabled
   efk: disabled
   freshpod: disabled
   gvisor: disabled
   helm-tiller: disabled
   ingress: disabled
   ingress-dns: disabled
   logviewer: disabled
   metrics-server: disabled
   nvidia-driver-installer: disabled
   nvidia-gpu-device-plugin: disabled
   registry: disabled
   registry-creds: disabled
   storage-provisioner: enabled
   storage-provisioner-gluster: disabled
   ```

<!--
2. Enable an addon, for example, `metrics-server`:
-->
2. 启用插件，例如 `metrics-server`：

   ```shell
   minikube addons enable metrics-server
   ```

   <!--
   The output is similar to:
   -->

   输出结果类似于这样：

   ```
   The 'metrics-server' addon is enabled
   ```

<!--
3. View the Pod and Service you created:
-->
3. 查看创建的 Pod 和 Service：

   ```shell
   kubectl get pod,svc -n kube-system
   ```

   <!--
   The output is similar to:
   -->

   输出结果类似于这样：

   ```
   NAME                                        READY     STATUS    RESTARTS   AGE
   pod/coredns-5644d7b6d9-mh9ll                1/1       Running   0          34m
   pod/coredns-5644d7b6d9-pqd2t                1/1       Running   0          34m
   pod/metrics-server-67fb648c5                1/1       Running   0          26s
   pod/etcd-minikube                           1/1       Running   0          34m
   pod/influxdb-grafana-b29w8                  2/2       Running   0          26s
   pod/kube-addon-manager-minikube             1/1       Running   0          34m
   pod/kube-apiserver-minikube                 1/1       Running   0          34m
   pod/kube-controller-manager-minikube        1/1       Running   0          34m
   pod/kube-proxy-rnlps                        1/1       Running   0          34m
   pod/kube-scheduler-minikube                 1/1       Running   0          34m
   pod/storage-provisioner                     1/1       Running   0          34m

   NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
   service/metrics-server         ClusterIP   10.96.241.45    <none>        80/TCP              26s
   service/kube-dns               ClusterIP   10.96.0.10      <none>        53/UDP,53/TCP       34m
   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
   ```

<!--
4. Disable `metrics-server`:
-->
4. 禁用 `metrics-server`：

   ```shell
   minikube addons disable metrics-server
   ```

   <!--
   The output is similar to:
   -->

   输出结果类似于这样：

   ```
   metrics-server was successfully disabled
   ```

<!--
## Clean up

Now you can clean up the resources you created in your cluster:
-->
## 清理

现在可以清理你在集群中创建的资源：

```shell
kubectl delete service hello-node
kubectl delete deployment hello-node
```

<!--
Optionally, stop the Minikube virtual machine (VM):
-->
可选地，停止 Minikube 虚拟机（VM）：

```shell
minikube stop
```

<!--
Optionally, delete the Minikube VM:
-->
可选地，删除 Minikube 虚拟机（VM）：

```shell
minikube delete
```

## {{% heading "whatsnext" %}}

<!--
* Learn more about [Deployment objects](/docs/concepts/workloads/controllers/deployment/).
* Learn more about [Deploying applications](/docs/tasks/run-application/run-stateless-application-deployment/).
* Learn more about [Service objects](/docs/concepts/services-networking/service/).
-->
* 进一步了解 [Deployment 对象](/zh/docs/concepts/workloads/controllers/deployment/)。
* 进一步了解[部署应用](/zh/docs/tasks/run-application/run-stateless-application-deployment/)。
* 进一步了解 [Service 对象](/zh/docs/concepts/services-networking/service/)。