hapihu commented on a change in pull request #16780:
URL: https://github.com/apache/flink/pull/16780#discussion_r688646429
##########
File path:
docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
##########
@@ -88,94 +86,102 @@ You can tear down the cluster using the following commands:
$ kubectl delete -f jobmanager-session-deployment.yaml
```
-
{{< top >}}
-## Deployment Modes
+<a name="deployment-modes"></a>
-### Deploy Application Cluster
+## 部署模式
-A *Flink Application cluster* is a dedicated cluster which runs a single
application, which needs to be available at deployment time.
+### Application 集群模式
-A basic *Flink Application cluster* deployment in Kubernetes has three
components:
+*Flink Application 集群* 是运行单个 Application 的专用集群，部署集群时要保证该 Application 可用。
-* an *Application* which runs a *JobManager*
-* a *Deployment* for a pool of *TaskManagers*
-* a *Service* exposing the *JobManager's* REST and UI ports
+在 Kubernetes 上部署一个基本的 *Flink Application 集群* 时，一般包括下面三个组件：
-Check [the Application cluster specific resource
definitions](#application-cluster-resource-definitions) and adjust them
accordingly:
+* *Application* 作业，同时在该 *Application* 中运行 *JobManager*；
+* 运行若干个 TaskManager 的 Deployment；
+* 暴露 JobManager 上 REST 和 UI 端口的 Service；
-The `args` attribute in the `jobmanager-job.yaml` has to specify the main
class of the user job.
-See also [how to specify the JobManager arguments]({{< ref
"docs/deployment/resource-providers/standalone/docker"
>}}#jobmanager-additional-command-line-arguments) to understand
-how to pass other `args` to the Flink image in the `jobmanager-job.yaml`.
+检查 [Application 集群资源定义](#application-cluster-resource-definitions) 并相应地调整它们：
-The *job artifacts* should be available from the `job-artifacts-volume` in
[the resource definition examples](#application-cluster-resource-definitions).
-The definition examples mount the volume as a local directory of the host
assuming that you create the components in a minikube cluster.
-If you do not use a minikube cluster, you can use any other type of volume,
available in your Kubernetes cluster, to supply the *job artifacts*.
-Alternatively, you can build [a custom image]({{< ref
"docs/deployment/resource-providers/standalone/docker"
>}}#advanced-customization) which already contains the artifacts instead.
+`jobmanager-job.yaml` 中的 `args` 属性必须指定用户作业的主类。也可以参考[如何设置 JobManager 参数]({{<
ref "docs/deployment/resource-providers/standalone/docker"
>}}#jobmanager-additional-command-line-arguments)来了解如何将额外的 `args` 传递给
`jobmanager-job.yaml` 配置中指定的 Flink 镜像。
-After creating [the common cluster
components](#common-cluster-resource-definitions), use [the Application cluster
specific resource definitions](#application-cluster-resource-definitions) to
launch the cluster with the `kubectl` command:
+*job artifacts* 参数必须可以从 [资源定义示例](#application-cluster-resource-definitions) 中的
`job-artifacts-volume` 处获取。假如是在 minikube 集群中创建这些组件，那么定义示例中的
job-artifacts-volume 可以挂载为主机的本地目录。如果不使用 minikube 集群，那么可以使用 Kubernetes
集群中任何其它可用类型的 volume 来提供 *job artifacts* 。此外，还可以构建一个已经包含 *job artifacts*
参数的[自定义镜像](({{< ref "docs/deployment/resource-providers/standalone/docker"
>}}#advanced-customization))。
+
+在创建[通用集群组件](#common-cluster-resource-definitions)后，指定 [Application
集群资源定义](#application-cluster-resource-definitions)文件，执行 `kubectl` 命令来启动 Flink
Application 集群：
```sh
$ kubectl create -f jobmanager-job.yaml
$ kubectl create -f taskmanager-job-deployment.yaml
```
-To terminate the single application cluster, these components can be deleted
along with [the common ones](#common-cluster-resource-definitions)
-with the `kubectl` command:
+要停止单个 application 集群，可以使用 `kubectl` 命令来删除相应组件以及
[通用集群资源](#common-cluster-resource-definitions)对应的组件 ：
```sh
$ kubectl delete -f taskmanager-job-deployment.yaml
$ kubectl delete -f jobmanager-job.yaml
```
-### Per-Job Cluster Mode
-Flink on Standalone Kubernetes does not support the Per-Job Cluster Mode.
+### Per-Job 集群模式
Review comment:
ok,i'll modify it
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
