hapihu commented on a change in pull request #16780:
URL: https://github.com/apache/flink/pull/16780#discussion_r688644466



##########
File path: 
docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
##########
@@ -25,61 +25,59 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-# Kubernetes Setup
+# Kubernetes 安装
 
-## Getting Started
+<a name="getting-started"></a>
 
-This *Getting Started* guide describes how to deploy a *Session cluster* on 
[Kubernetes](https://kubernetes.io).
+## 入门
 
-### Introduction
+本 *入门* 指南描述了如何在 [Kubernetes](https://kubernetes.io) 上部署 *Flink Seesion 集群*。
 
-This page describes deploying a [standalone]({{< ref 
"docs/deployment/resource-providers/standalone/overview" >}}) Flink cluster on 
top of Kubernetes, using Flink's standalone deployment.
-We generally recommend new users to deploy Flink on Kubernetes using [native 
Kubernetes deployments]({{< ref 
"docs/deployment/resource-providers/native_kubernetes" >}}).
+### 介绍
 
-### Preparation
+本文描述了如何使用 Flink standalone 部署模式在 Kubernetes 上部署 [standalone]({{< ref 
"docs/deployment/resource-providers/standalone/overview" >}}) 模式的 Flink 
集群。通常我们建议新用户使用 [native Kubernetes 部署]({{< ref 
"docs/deployment/resource-providers/native_kubernetes" >}}) 模式在 Kubernetes上部署 
Flink。
 
-This guide expects a Kubernetes environment to be present. You can ensure that 
your Kubernetes setup is working by running a command like `kubectl get nodes`, 
which lists all connected Kubelets. 
+### 准备
 
-If you want to run Kubernetes locally, we recommend using 
[MiniKube](https://minikube.sigs.k8s.io/docs/start/).
+本指南假设存在一个 Kubernets 的运行环境。可以通过运行 `kubectl get nodes` 命令来确保 Kubernetes 
环境运行正常,该命令展示所有连接到 Kubernets 集群的 node 节点信息。
+
+如果想在本地运行 Kubernetes,建议使用 [MiniKube](https://minikube.sigs.k8s.io/docs/start/)。
 
 {{< hint info >}}
-If using MiniKube please make sure to execute `minikube ssh 'sudo ip link set 
docker0 promisc on'` before deploying a Flink cluster. Otherwise Flink 
components are not able to reference themselves through a Kubernetes service.
+如果使用 MiniKube,请确保在部署 Flink 集群之前先执行 `minikube ssh 'sudo ip link set docker0 
promisc on'`,否则 Flink 组件不能自动地将自己映射到 Kubernetes Service 中。
 {{< /hint >}}
 
-### Starting a Kubernetes Cluster (Session Mode)
+### Kubernetes 上的 Flink session 集群
 
-A *Flink Session cluster* is executed as a long-running Kubernetes Deployment. 
You can run multiple Flink jobs on a *Session cluster*.
-Each job needs to be submitted to the cluster after the cluster has been 
deployed.
+*Flink session 集群* 是以一种长期运行的 Kubernetes Deployment 形式执行的。可以在一个 *session 集群* 
上运行多个 Flink 作业。当然,只有 session 集群部署好以后才可以在上面提交 Flink 作业。
 
-A *Flink Session cluster* deployment in Kubernetes has at least three 
components:
+在 Kubernetes 上部署一个基本的 *Flink session 集群* 时,一般包括下面三个组件:
 
-* a *Deployment* which runs a [JobManager]({{< ref "docs/concepts/glossary" 
>}}#flink-jobmanager)
-* a *Deployment* for a pool of [TaskManagers]({{< ref "docs/concepts/glossary" 
>}}#flink-taskmanager)
-* a *Service* exposing the *JobManager's* REST and UI ports
+* 运行 [JobManager]({{< ref "docs/concepts/glossary" >}}#flink-jobmanager) 的 
*Deployment*;
+* 运行 [TaskManagers]({{< ref "docs/concepts/glossary" >}}#flink-taskmanager) 的 
*Deployment*;
+* 暴露 *JobManager* 上 REST 和 UI 端口的 *Service*;
 
-Using the file contents provided in the [the common resource 
definitions](#common-cluster-resource-definitions), create the following files, 
and create the respective components with the `kubectl` command:
+使用 [通用集群资源定义](#common-cluster-resource-definitions)中提供的文件内容来创建以下文件,并使用 
`kubectl` 命令来创建相应的组件:
 
 ```sh
-    # Configuration and service definition
+    # configmap 和 service 的定义

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]


Reply via email to