Merge pull request #39024 from Zhuzhenghao/web-ui-dashboard.md
[zh-cn] Sync web-ui-dashboard.mdpull/39036/head
Kubernetes Prow Robot
GitHub
commit
4761ec47db
|
|
@ -6,6 +6,7 @@ card:
|
|||
name: tasks
|
||||
weight: 30
|
||||
title: 使用 Web 界面 Dashboard
|
||||
description: 部署并访问 Web 界面（Kubernetes 仪表板）。
|
||||
---
|
||||
<!--
|
||||
reviewers:
|
||||
|
|
@ -14,6 +15,8 @@ reviewers:
|
|||
- shu-mutou
|
||||
- mikedanese
|
||||
title: Deploy and Access the Kubernetes Dashboard
|
||||
description: >-
|
||||
Deploy the web UI (Kubernetes Dashboard) and access it.
|
||||
content_type: concept
|
||||
weight: 10
|
||||
card:
|
||||
|
|
@ -57,7 +60,7 @@ The Dashboard UI is not deployed by default. To deploy it, run the following com
|
|||
默认情况下不会部署 Dashboard。可以通过以下命令部署：
|
||||
|
||||
```
|
||||
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.6.1/aio/deploy/recommended.yaml
|
||||
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
|
||||
```
|
||||
|
||||
<!--
|
||||
|
|
@ -66,14 +69,14 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.6.1/a
|
|||
To protect your cluster data, Dashboard deploys with a minimal RBAC configuration by default.
|
||||
Currently, Dashboard only supports logging in with a Bearer Token.
|
||||
To create a token for this demo, you can follow our guide on
|
||||
[creating a sample user](https://github.com/kubernetes/dashboard/wiki/Creating-sample-user).
|
||||
[creating a sample user](https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md).
|
||||
-->
|
||||
## 访问 Dashboard 用户界面
|
||||
|
||||
为了保护你的集群数据，默认情况下，Dashboard 会使用最少的 RBAC 配置进行部署。
|
||||
当前，Dashboard 仅支持使用 Bearer 令牌登录。
|
||||
要为此样本演示创建令牌，你可以按照
|
||||
[创建示例用户](https://github.com/kubernetes/dashboard/wiki/Creating-sample-user)
|
||||
[创建示例用户](https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md)
|
||||
上的指南进行操作。
|
||||
|
||||
<!--
|
||||
|
|
@ -291,7 +294,7 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
|
||||
<!--
|
||||
Dashboard offers all available secrets in a dropdown list, and allows you to create a new secret.
|
||||
The secret name must follow the DNS domain name syntax, e.g. `new.image-pull.secret`.
|
||||
The secret name must follow the DNS domain name syntax, for example `new.image-pull.secret`.
|
||||
The content of a secret must be base64-encoded and specified in a
|
||||
[`.dockercfg`](/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod) file.
|
||||
The secret name may consist of a maximum of 253 characters.
|
||||
|
|
@ -310,21 +313,29 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
如果创建失败，则不会使用任何 Secret。
|
||||
|
||||
<!--
|
||||
- **CPU requirement (cores)** and **Memory requirement (MiB)**: You can specify the minimum [resource limits](/docs/tasks/configure-pod-container/limit-range/) for the container. By default, Pods run with unbounded CPU and memory limits.
|
||||
- **CPU requirement (cores)** and **Memory requirement (MiB)**:
|
||||
You can specify the minimum [resource limits](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/)
|
||||
for the container. By default, Pods run with unbounded CPU and memory limits.
|
||||
-->
|
||||
- **CPU 需求（核数）** 和 **内存需求（MiB）**：你可以为容器定义最小的
|
||||
[资源限制](/zh-cn/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/)。
|
||||
默认情况下，Pod 没有 CPU 和内存限制。
|
||||
|
||||
<!--
|
||||
- **Run command** and **Run command arguments**: By default, your containers run the specified Docker image's default [entrypoint command](/docs/user-guide/containers/#containers-and-commands). You can use the command options and arguments to override the default.
|
||||
- **Run command** and **Run command arguments**:
|
||||
By default, your containers run the specified Docker image's default
|
||||
[entrypoint command](/docs/tasks/inject-data-application/define-command-argument-container/).
|
||||
You can use the command options and arguments to override the default.
|
||||
-->
|
||||
- **运行命令**和**运行命令参数**：默认情况下，你的容器会运行 Docker 镜像的默认
|
||||
[入口命令](/zh-cn/docs/tasks/inject-data-application/define-command-argument-container/)。
|
||||
你可以使用 command 选项覆盖默认值。
|
||||
|
||||
<!--
|
||||
- **Run as privileged**: This setting determines whether processes in [privileged containers](/docs/user-guide/pods/#privileged-mode-for-pod-containers) are equivalent to processes running as root on the host. Privileged containers can make use of capabilities like manipulating the network stack and accessing devices.
|
||||
- **Run as privileged**: This setting determines whether processes in
|
||||
[privileged containers](/docs/concepts/workloads/pods/#privileged-mode-for-containers)
|
||||
are equivalent to processes running as root on the host.
|
||||
Privileged containers can make use of capabilities like manipulating the network stack and accessing devices.
|
||||
-->
|
||||
- **以特权模式运行**：这个设置决定了在
|
||||
[特权容器](/zh-cn/docs/concepts/workloads/pods/#privileged-mode-for-containers)
|
||||
|
|
@ -344,7 +355,7 @@ If needed, you can expand the **Advanced options** section where you can specify
|
|||
|
||||
Kubernetes supports declarative configuration.
|
||||
In this style, all configuration is stored in manifests (YAML or JSON configuration files).
|
||||
The manifests use the Kubernetes [API](/docs/concepts/overview/kubernetes-api/) resource schemas.
|
||||
The manifests use Kubernetes [API](/docs/concepts/overview/kubernetes-api/) resource schemas.
|
||||
-->
|
||||
### 上传 YAML 或者 JSON 文件
|
||||
|
||||
|
|
@ -354,7 +365,7 @@ Kubernetes 支持声明式配置。所有的配置都存储在清单文件
|
|||
|
||||
<!--
|
||||
As an alternative to specifying application details in the deploy wizard,
|
||||
you can define your application one or more manifests, and upload the files using Dashboard.
|
||||
you can define your application in one or more manifests, and upload the files using Dashboard.
|
||||
-->
|
||||
作为一种替代在部署向导中指定应用详情的方式，你可以在一个或多个清单文件中定义应用，并且使用
|
||||
Dashboard 上传文件。
|
||||
|
|
@ -384,7 +395,7 @@ Dashboard shows most Kubernetes object kinds and groups them in a few menu categ
|
|||
Dashboard 展示大部分 Kubernetes 对象，并将它们分组放在几个菜单类别中。
|
||||
|
||||
<!--
|
||||
#### Admin Overview
|
||||
#### Admin overview
|
||||
|
||||
For cluster and namespace administrators, Dashboard lists Nodes, Namespaces and PersistentVolumes and has detail views for them.
|
||||
Node list view contains CPU and memory usage metrics aggregated across all Nodes.
|
||||
|
|
@ -401,7 +412,7 @@ allocated resources, events and pods running on the node.
|
|||
#### Workloads
|
||||
|
||||
Shows all applications running in the selected namespace.
|
||||
The view lists applications by workload kind (e.g., Deployments, ReplicaSets, Stateful Sets, etc.).
|
||||
The view lists applications by workload kind (for example: Deployments, ReplicaSets, StatefulSets).
|
||||
Each workload kind can be viewed separately.
|
||||
The lists summarize actionable information about the workloads,
|
||||
such as the number of ready pods for a ReplicaSet or current memory usage for a Pod.
|
||||
|
|
@ -409,13 +420,13 @@ such as the number of ready pods for a ReplicaSet or current memory usage for a
|
|||
#### 负载
|
||||
|
||||
显示选中的名字空间中所有运行的应用。
|
||||
视图按照负载类型（如 Deployment、ReplicaSet、StatefulSet 等）罗列应用，并且每种负载都可以单独查看。
|
||||
视图按照负载类型（例如：Deployment、ReplicaSet、StatefulSet）罗列应用，并且每种负载都可以单独查看。
|
||||
列表总结了关于负载的可执行信息，比如一个 ReplicaSet 的就绪状态的 Pod 数量，或者目前一个 Pod 的内存用量。
|
||||
|
||||
<!--
|
||||
Detail views for workloads show status and specification information and
|
||||
surface relationships between objects.
|
||||
For example, Pods that Replica Set is controlling or New ReplicaSets and HorizontalPodAutoscalers for Deployments.
|
||||
For example, Pods that ReplicaSet is controlling or new ReplicaSets and HorizontalPodAutoscalers for Deployments.
|
||||
-->
|
||||
工作负载的详情视图展示了对象的状态、详细信息和相互关系。
|
||||
例如，ReplicaSet 所控制的 Pod，或者 Deployment 所关联的新 ReplicaSet 和
|
||||
|
|
@ -441,11 +452,11 @@ Storage view shows PersistentVolumeClaim resources which are used by application
|
|||
存储视图展示持久卷申领（PVC）资源，这些资源被应用程序用来存储数据。
|
||||
|
||||
<!--
|
||||
#### Config Maps and Secrets
|
||||
#### ConfigMaps and Secrets {#config-maps-and-secrets}
|
||||
|
||||
Shows all Kubernetes resources that are used for live configuration of applications running in clusters. The view allows for editing and managing config objects and displays secrets hidden by default.
|
||||
-->
|
||||
#### ConfigMap 和 Secret
|
||||
#### ConfigMap 和 Secret {#config-maps-and-secrets}
|
||||
|
||||
展示的所有 Kubernetes 资源是在集群中运行的应用程序的实时配置。
|
||||
通过这个视图可以编辑和管理配置对象，并显示那些默认隐藏的 Secret。
|
||||
|
|
@ -453,7 +464,8 @@ Shows all Kubernetes resources that are used for live configuration of applicati
|
|||
<!--
|
||||
#### Logs viewer
|
||||
|
||||
Pod lists and detail pages link to logs viewer that is built into Dashboard. The viewer allows for drilling down logs from containers belonging to a single Pod.
|
||||
Pod lists and detail pages link to a logs viewer that is built into Dashboard.
|
||||
The viewer allows for drilling down logs from containers belonging to a single Pod.
|
||||
-->
|
||||
#### 日志查看器
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue