wuchong commented on a change in pull request #8986: [FLINK-13092][docs-zh] 
Translate "Kubernetes" page into Chinese
URL: https://github.com/apache/flink/pull/8986#discussion_r300867831
 
 

 ##########
 File path: docs/ops/deployment/kubernetes.zh.md
 ##########
 @@ -28,72 +28,75 @@ This page describes how to deploy a Flink job and session 
cluster on [Kubernetes
 * This will be replaced by the TOC
 {:toc}
 
-## Setup Kubernetes
+## 安装Kubernetes
 
-Please follow [Kubernetes' setup guide](https://kubernetes.io/docs/setup/) in 
order to deploy a Kubernetes cluster.
-If you want to run Kubernetes locally, we recommend using 
[MiniKube](https://kubernetes.io/docs/setup/minikube/).
+请先参阅[Kubernetes安装教程](https://kubernetes.io/docs/setup/)来部署Kubernetes集群。
+
+如果想在本地运行Kubernetes 
,这里建议使用[MiniKube](https://kubernetes.io/docs/setup/minikube/)。
 
 <div class="alert alert-info" markdown="span">
-  <strong>Note:</strong> 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 self reference themselves through 
a Kubernetes service. 
+  <strong>注意:</strong> 如果使用MiniKube 请确保在部署Flink集群之前先执行 `minikube ssh 'sudo ip 
link set docker0 promisc on'` ,否则Flink组件不能自动地将自己映射到Kubernetes Service中。
 </div>
 
-## Flink session cluster on Kubernetes
 
-A Flink session cluster is executed as a long-running Kubernetes Deployment. 
-Note that 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.
+## 部署在Kubernetes上的Flink session集群
+
+Flink 
session集群执行时是作为Kubernetes上长期运行的Deployment。这里值得注意的是,可以在一个session集群上运行多个Flink作业。当然,只有session集群部署好以后才可以在上面提交Flink作业。
 
 Review comment:
   ```suggestion
   Flink session 集群是以一种长期运行的 Kubernetes Deployment 
形式执行的。这里值得注意的是,可以在一个session集群上运行多个Flink作业。当然,只有session集群部署好以后才可以在上面提交Flink作业。
   ```

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to