hapihu commented on a change in pull request #16780:
URL: https://github.com/apache/flink/pull/16780#discussion_r688626134
##########
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) 并相应地调整它们：
Review comment:
Ok, that sounds more smooth.
--
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]
