This is an automated email from the ASF dual-hosted git repository.
trohrmann pushed a commit to branch release-1.13
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/release-1.13 by this push:
new 0b1078c [FLINK-22264][docs] Fix misleading statement about Flink Job
Cluster Kubernetes Support in Flink Architecture page
0b1078c is described below
commit 0b1078c7298778880762dd5d686b5412f6b5309b
Author: fuyli <[email protected]>
AuthorDate: Tue Apr 13 19:00:56 2021 -0700
[FLINK-22264][docs] Fix misleading statement about Flink Job Cluster
Kubernetes Support in Flink Architecture page
[FLINK-22264][docs] Add Chinese documentation
This closes #15602.
---
docs/content.zh/docs/concepts/flink-architecture.md | 5 ++++-
docs/content/docs/concepts/flink-architecture.md | 5 ++++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/docs/content.zh/docs/concepts/flink-architecture.md
b/docs/content.zh/docs/concepts/flink-architecture.md
index ec82643..9b296bc 100644
--- a/docs/content.zh/docs/concepts/flink-architecture.md
+++ b/docs/content.zh/docs/concepts/flink-architecture.md
@@ -113,7 +113,7 @@ Flink 应用程序的作业可以被提交到长期运行的 [Flink Session 集
### Flink Job 集群
-* **集群生命周期**：在 Flink Job 集群中，可用的集群管理器（例如 YARN 或
Kubernetes）用于为每个提交的作业启动一个集群，并且该集群仅可用于该作业。在这里，客户端首先从集群管理器请求资源启动
JobManager，然后将作业提交给在这个进程中运行的 Dispatcher。然后根据作业的资源请求惰性的分配
TaskManager。一旦作业完成，Flink Job 集群将被拆除。
+* **集群生命周期**：在 Flink Job 集群中，可用的集群管理器（例如
YARN）用于为每个提交的作业启动一个集群，并且该集群仅可用于该作业。在这里，客户端首先从集群管理器请求资源启动
JobManager，然后将作业提交给在这个进程中运行的 Dispatcher。然后根据作业的资源请求惰性的分配
TaskManager。一旦作业完成，Flink Job 集群将被拆除。
* **资源隔离**：JobManager 中的致命错误仅影响在 Flink Job 集群中运行的一个作业。
@@ -122,6 +122,9 @@ Flink 应用程序的作业可以被提交到长期运行的 [Flink Session 集
{{< hint info >}}
以前，Flink Job 集群也被称为<i> job (or per-job) 模式</i>下的 Flink 集群。
{{< /hint >}}
+{{< hint info >}}
+Kubernetes 不支持 Flink Job 集群。 请参考 [Standalone Kubernetes]({{< ref
"docs/deployment/resource-providers/standalone/kubernetes"
>}}#per-job-cluster-mode) 和 [Native Kubernetes]({{< ref
"docs/deployment/resource-providers/native_kubernetes"
>}}#per-job-cluster-mode)。
+{{< /hint >}}
### Flink Application 集群
diff --git a/docs/content/docs/concepts/flink-architecture.md
b/docs/content/docs/concepts/flink-architecture.md
index 3fb4d4d..62e32bb 100644
--- a/docs/content/docs/concepts/flink-architecture.md
+++ b/docs/content/docs/concepts/flink-architecture.md
@@ -204,7 +204,7 @@ Formerly, a Flink Session Cluster was also known as a Flink
Cluster in `session
### Flink Job Cluster
* **Cluster Lifecycle**: in a Flink Job Cluster, the available cluster manager
- (like YARN or Kubernetes) is used to spin up a cluster for each submitted job
+ (like YARN) is used to spin up a cluster for each submitted job
and this cluster is available to that job only. Here, the client first
requests resources from the cluster manager to start the JobManager and
submits the job to the Dispatcher running inside this process. TaskManagers
@@ -222,6 +222,9 @@ Formerly, a Flink Session Cluster was also known as a Flink
Cluster in `session
{{< hint info >}}
Formerly, a Flink Job Cluster was also known as a Flink Cluster in `job (or
per-job) mode`.
{{< /hint >}}
+{{< hint info >}}
+Kubernetes doesn't support Flink Job Cluster. See details in [Standalone
Kubernetes]({{< ref "docs/deployment/resource-providers/standalone/kubernetes"
>}}#per-job-cluster-mode) and [Native Kubernetes]({{< ref
"docs/deployment/resource-providers/native_kubernetes"
>}}#per-job-cluster-mode).
+{{< /hint >}}
### Flink Application Cluster
