[PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai opened a new pull request, #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809 ## What is the purpose of the change *(For example: This pull request adds a new feature to periodically create and maintain savepoints through the `FlinkDeployment` custom resource.)* ## Brief change log *(for example:)* - *Periodic savepoint trigger is introduced to the custom resource* - *The operator checks on reconciliation whether the required time has passed* - *The JobManager's dispose savepoint API is used to clean up obsolete savepoints* ## Verifying this change *(Please pick either of the following options)* This change is a trivial rework / code cleanup without any test coverage. *(or)* This change is already covered by existing tests, such as *(please describe tests)*. *(or)* This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment with large payloads (100MB)* - *Extended integration test for recovery after master (JobManager) failure* - *Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.* ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / no) - The public API, i.e., is any changes to the `CustomResourceDescriptors`: (yes / no) - Core observer or reconciler logic that is regularly executed: (yes / no) ## Documentation - Does this pull request introduce a new feature? (yes / no) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#issuecomment-2028542576  -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545534053 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -26,55 +26,55 @@ under the License. # Architecture Review Comment: It's not clear to me whether the title should be translated -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545539220 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -26,55 +26,55 @@ under the License. # Architecture Review Comment: > It's not clear to me whether the title should be translated hi, @caicancai Thx for the pr. It would be better to translate it like other translated pages~ -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545572383 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -26,55 +26,55 @@ under the License. # Architecture Review Comment: Thank you for your reply, done -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545922843 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: Maybe the precise announcement is here https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications Would you mind using the anchor to update it ? thx~ -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545923010
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,57 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+# 架构
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+## 控制平面
Review Comment:
ditto
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,57 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+# 架构
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator观察 Flink 资源的当前状态（如
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545922843 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: Maybe the precise announcement is here https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications https://github.com/apache/flink-kubernetes-operator/assets/64569824/604a6c86-2f1e-46a8-b934-d5d44a21923e";> Would you mind using the anchor to update it ? thx~ -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545936400 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: a name="Architecture"> ？ -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545936400 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545936400 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545936742 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: Thank you for your review, I have added it, please check if it is correct -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545936742 ## docs/content.zh/docs/concepts/architecture.md: ## @@ -24,57 +24,57 @@ specific language governing permissions and limitations under the License. --> -# Architecture +# 架构 Review Comment: @RocMarshal Thank you for your review, I have added it, please check if it is correct -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1545999604
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
Review Comment:
```suggestion
```
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
Review Comment:
```suggestion
```
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1554829325
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
Review Comment:
How about update `Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装`
to `可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装 Operator`?
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
Review Comment:
`操作员` -> `Operator`,
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#issuecomment-2041350690 Also, it's better to update the PR description. We can update these items or remove them if you think they are unneeded, thanks~ -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#issuecomment-2053635501 > Thanks @caicancai for the great work! > > Overall is good for me, i left some comments, please take a look in your free time, thanks a lot. > > I wanna mention some common issues here due to we have a lot of pages will be translated in the future. > > 1. Can we keep some Terminology (do not translate them)? such as: operator, deployment, etc > 2. We don't need to translate for every English word. Try to ensure that the translated Chinese is easy to understand and not awkward to read. (尽量保证翻译后的中文通俗易懂，读起来不别扭。) Thanks for the reminder, I will improve 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#issuecomment-2056898849 cc @1996fanrui -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1566812379
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
Review Comment:
> `当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes 集群以达到所需状态，作为其协调循环的一部分。` -> `当
Operator 接收到新的资源更新时，它将调整 Kubernetes 集群以达到所需状态，这个调整将作为其协调循环的一部分。`
Is it not updated?
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1566817400
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
-The Operator is built with the [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the
[Native Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
for launching Flink deployments and submitting jobs under the hood. The Java
Operator SDK is a higher level framework and related tooling to support writing
Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native
kubernetes integration itself is using the [Fabric8 Kubernetes
Client](https://github.com/fabric8io/kubernetes-client) to interact with the
Kubernetes API Server.
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator观察 Flink 资源的当前状态（如果先前已部署）
+3. Operator验证提交的资源更改
+4. Operator协调任何必要的更改并执行升级
-## Flink Resource Lifecycle
+CR 可以随时在集群上（重新）应用。Operator 通过不断调整来模拟所需状态，直到当前状态变为所需状态。Operator
中的所有生命周期管理操作都是使用这个非常简单的原则实现的。
-The Operator manages the lifecycle of Flink resources. The following chart
illustrates the different possible states and transitions:
+Operator [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk)和使用 [Native
Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
在幕后启动 Flink 部署和提交作业。Java Operator SDK 是一个更高级别的框架和相关工具，用于支持使用 Java 编写
Kubernetes Operator。Java Operator SDK 和 Flink 的本地 Kubernetes 集成本身都使用 [Fabric8
Kubernetes Client](
-{{< img src="/img/concepts/resource_lifecycle.svg" alt="Flink Resource
Lifecycle" >}}
+
-**We ca
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1566828007
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
Review Comment:
Sorry, I forgot to submit
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1566834001
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
-The Operator is built with the [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the
[Native Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
for launching Flink deployments and submitting jobs under the hood. The Java
Operator SDK is a higher level framework and related tooling to support writing
Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native
kubernetes integration itself is using the [Fabric8 Kubernetes
Client](https://github.com/fabric8io/kubernetes-client) to interact with the
Kubernetes API Server.
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator观察 Flink 资源的当前状态（如果先前已部署）
+3. Operator验证提交的资源更改
+4. Operator协调任何必要的更改并执行升级
-## Flink Resource Lifecycle
+CR 可以随时在集群上（重新）应用。Operator 通过不断调整来模拟所需状态，直到当前状态变为所需状态。Operator
中的所有生命周期管理操作都是使用这个非常简单的原则实现的。
-The Operator manages the lifecycle of Flink resources. The following chart
illustrates the different possible states and transitions:
+Operator [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk)和使用 [Native
Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
在幕后启动 Flink 部署和提交作业。Java Operator SDK 是一个更高级别的框架和相关工具，用于支持使用 Java 编写
Kubernetes Operator。Java Operator SDK 和 Flink 的本地 Kubernetes 集成本身都使用 [Fabric8
Kubernetes Client](
-{{< img src="/img/concepts/resource_lifecycle.svg" alt="Flink Resource
Lifecycle" >}}
+
-**We ca
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1566848357
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,66 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整deployment生命周期。可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装
Operator。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个Flink 部署到受托管的 namespaces。描述
`FlinkDeployment` 模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD
类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与Operator进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当 Operator 接收到新的资源更新时，它将调整 Kubernetes
集群以达到所需状态，这个调整将作为其协调循环的一部分。初始循环包括以下高级步骤：
-The Operator is built with the [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the
[Native Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
for launching Flink deployments and submitting jobs under the hood. The Java
Operator SDK is a higher level framework and related tooling to support writing
Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native
kubernetes integration itself is using the [Fabric8 Kubernetes
Client](https://github.com/fabric8io/kubernetes-client) to interact with the
Kubernetes API Server.
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator 观察 Flink 资源的当前状态（如果先前已部署）
+3. Operator 验证提交的资源更改
+4. Operator 协调任何必要的更改并执行升级
-## Flink Resource Lifecycle
+CR 可以随时在集群上（重新）应用。Operator 通过不断调整来模拟期望的状态，直到当前状态变为期望的状态。Operator
中的所有生命周期管理操作都是使用这个非常简单的原则实现的。
-The Operator manages the lifecycle of Flink resources. The following chart
illustrates the different possible states and transitions:
+Operator 使用 [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) 构建，并使用 [Native
Kubernetes Integration](https://nightlies.apache.org
/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
用于启动 Flink deployment 并在后台提交作业。
+Java Operator SDK 是一个更高级别的框架和相关工具，用于支持使用 Java 编写 Kubernetes Operator。Java
Operator SDK 和 Flink 的原生 kubernetes 集成本身都使用 [Fabric8 Kubernetes
客户端](https://github.com/fabric8io/kubernetes-client) 与 Kub
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1573750776
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,66 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整deployment生命周期。可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装
Operator。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个Flink 部署到受托管的 namespaces。描述
`FlinkDeployment` 模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD
类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与Operator进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当 Operator 接收到新的资源更新时，它将调整 Kubernetes
集群以达到所需状态，这个调整将作为其协调循环的一部分。初始循环包括以下高级步骤：
-The Operator is built with the [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the
[Native Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
for launching Flink deployments and submitting jobs under the hood. The Java
Operator SDK is a higher level framework and related tooling to support writing
Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native
kubernetes integration itself is using the [Fabric8 Kubernetes
Client](https://github.com/fabric8io/kubernetes-client) to interact with the
Kubernetes API Server.
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator 观察 Flink 资源的当前状态（如果先前已部署）
+3. Operator 验证提交的资源更改
+4. Operator 协调任何必要的更改并执行升级
-## Flink Resource Lifecycle
+CR 可以随时在集群上（重新）应用。Operator 通过不断调整来模拟期望的状态，直到当前状态变为期望的状态。Operator
中的所有生命周期管理操作都是使用这个非常简单的原则实现的。
-The Operator manages the lifecycle of Flink resources. The following chart
illustrates the different possible states and transitions:
+Operator 使用 [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) 构建，并使用 [Native
Kubernetes Integration](https://nightlies.apache.org
/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
用于启动 Flink deployment 并在后台提交作业。
+Java Operator SDK 是一个更高级别的框架和相关工具，用于支持使用 Java 编写 Kubernetes Operator。Java
Operator SDK 和 Flink 的原生 kubernetes 集成本身都使用 [Fabric8 Kubernetes
客户端](https://github.com/fabric8io/kubernetes-client) 与 Kube
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1574071090
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,66 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink 应用程序的完整 deployment
生命周期。可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装
Operator。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个 Flink 部署到受托管的 namespaces 。描述
`FlinkDeployment` 模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD
类型的任何资源之前注册声明，注册过程有时需要几秒钟。
Review Comment:
1. `Flink 部署` -> `Flink deployments `
2. How about translate `schema` to `结构` instead of `模式`?
3. As
https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications
mentioned, `是一个集群范围的资源`, we don't need `一个` here.
https://github.com/apache/flink-kubernetes-operator/assets/38427477/4b5153c8-73b1-4708-9bb4-83255f7d29a6";>
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [k
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1574091929
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,66 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink 应用程序的完整 deployment
生命周期。可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装
Operator。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个 Flink 部署到受托管的 namespaces 。描述
`FlinkDeployment` 模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD
类型的任何资源之前注册声明，注册过程有时需要几秒钟。
Review Comment:
Sorry, I overlooked this, next time I should read it aloud to check
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1574098275
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,66 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink 应用程序的完整 deployment
生命周期。可以使用 [Helm](https://helm.sh) 在 Kubernetes 集群上安装
Operator。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个 Flink 部署到受托管的 namespaces 。描述
`FlinkDeployment` 模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD
类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/) 与
Operator 进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当 Operator 接收到新的资源更新时，它将调整 Kubernetes
集群以达到所需状态，这个调整将作为其协调循环的一部分。初始循环包括以下高级步骤：
-The Operator is built with the [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the
[Native Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
for launching Flink deployments and submitting jobs under the hood. The Java
Operator SDK is a higher level framework and related tooling to support writing
Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native
kubernetes integration itself is using the [Fabric8 Kubernetes
Client](https://github.com/fabric8io/kubernetes-client) to interact with the
Kubernetes API Server.
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator 观察 Flink 资源的当前状态（如果先前已部署）
+3. Operator 验证提交的资源更改
+4. Operator 协调任何必要的更改并执行升级
-## Flink Resource Lifecycle
+CR 可以随时在集群上（重新）应用。Operator 通过不断调整来模拟期望的状态，直到当前状态变为期望的状态。Operator
中的所有生命周期管理操作都是使用这个非常简单的原则实现的。
-The Operator manages the lifecycle of Flink resources. The following chart
illustrates the different possible states and transitions:
+Operator 使用 [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) 构建，并使用 [Native
Kubernetes Integration](https://nightlies.apache.org
/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
用于启动 Flink deployment 并在后台提交作业。
Review Comment:
done
--
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.
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #809:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/809#discussion_r1574216679
##
docs/content.zh/docs/concepts/architecture.md:
##
@@ -24,57 +24,65 @@ specific language governing permissions and limitations
under the License.
-->
-# Architecture
+
-Flink Kubernetes Operator (Operator) acts as a control plane to manage the
complete deployment lifecycle of Apache Flink applications. The Operator can be
installed on a Kubernetes cluster using [Helm](https://helm.sh). In most
production environments it is typically deployed in a designated namespace and
controls Flink deployments in one or more managed namespaces. The custom
resource definition (CRD) that describes the schema of a `FlinkDeployment` is a
cluster wide resource. For a CRD, the declaration must be registered before any
resources of that CRDs kind(s) can be used, and the registration process
sometimes takes a few seconds.
+# 架构
-{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
Architecture" >}}
-> Note: There is no support at this time for [upgrading or deleting CRDs using
Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
+Flink Kubernetes Operator（Operator）充当控制平面，用于管理 Apache Flink
应用程序的完整部署生命周期。Operator 可以使用 [Helm](https://helm.sh) 在 Kubernetes
集群上安装。在大多数生产环境中，它通常部署在指定的命名空间中，并控制一个或多个受管命名空间中的 Flink 部署。描述 `FlinkDeployment`
模式的自定义资源定义（CRD）是一个集群范围的资源。对于 CRD，必须在使用该 CRD 类型的任何资源之前注册声明，注册过程有时需要几秒钟。
-## Control Loop
-The Operator follow the Kubernetes principles, notably the [control
loop](https://kubernetes.io/docs/concepts/architecture/controller/):
+{{< img src="/img/concepts/architecture.svg" alt="Flink Kubernetes Operator
架构" >}}
+> Note: 目前不支持[使用 Helm 升级或删除
CRD](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
-{{< img src="/img/concepts/control_loop.svg" alt="Control Loop" >}}
+
-Users can interact with the operator using the Kubernetes command-line tool,
[kubectl](https://kubernetes.io/docs/tasks/tools/). The Operator continuously
tracks cluster events relating to the `FlinkDeployment` and `FlinkSessionJob`
custom resources. When the operator receives a new resource update, it will
take action to adjust the Kubernetes cluster to the desired state as part of
its reconciliation loop. The initial loop consists of the following high-level
steps:
+## 控制平面
+Operator 遵循 Kubernetes 原则，特别是
[控制平面](https://kubernetes.io/docs/concepts/architecture/controller/)：
-1. User submits a `FlinkDeployment`/`FlinkSessionJob` custom resource(CR)
using `kubectl`
-2. Operator observes the current status of the Flink resource (if previously
deployed)
-3. Operator validates the submitted resource change
-4. Operator reconciles any required changes and executes upgrades
+{{< img src="/img/concepts/control_loop.svg" alt="控制循环" >}}
-The CR can be (re)applied on the cluster any time. The Operator makes
continuous adjustments to imitate the desired state until the current state
becomes the desired state. All lifecycle management operations are realized
using this very simple principle in the Operator.
+用户可以使用 Kubernetes 命令行工具 [kubectl](https://kubernetes.io/docs/tasks/tools/)
与操作员进行交互。Operator 不断跟踪与 `FlinkDeployment` 和 `FlinkSessionJob`
自定义资源相关的集群事件。当操作员接收到新的资源更新时，它将采取行动，以调整 Kubernetes
集群以达到所需状态，作为其协调循环的一部分。初始循环包括以下高级步骤：
-The Operator is built with the [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk) and uses the
[Native Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
for launching Flink deployments and submitting jobs under the hood. The Java
Operator SDK is a higher level framework and related tooling to support writing
Kubernetes Operators in Java. Both the Java Operator SDK and Flink's native
kubernetes integration itself is using the [Fabric8 Kubernetes
Client](https://github.com/fabric8io/kubernetes-client) to interact with the
Kubernetes API Server.
+1. 用户使用 `kubectl` 提交 `FlinkDeployment`/`FlinkSessionJob` 自定义资源（CR）
+2. Operator观察 Flink 资源的当前状态（如果先前已部署）
+3. Operator验证提交的资源更改
+4. Operator协调任何必要的更改并执行升级
-## Flink Resource Lifecycle
+CR 可以随时在集群上（重新）应用。Operator 通过不断调整来模拟所需状态，直到当前状态变为所需状态。Operator
中的所有生命周期管理操作都是使用这个非常简单的原则实现的。
-The Operator manages the lifecycle of Flink resources. The following chart
illustrates the different possible states and transitions:
+Operator [Java Operator
SDK](https://github.com/java-operator-sdk/java-operator-sdk)和使用 [Native
Kubernetes
Integration](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/)
在幕后启动 Flink 部署和提交作业。Java Operator SDK 是一个更高级别的框架和相关工具，用于支持使用 Java 编写
Kubernetes Operator。Java Operator SDK 和 Flink 的本地 Kubernetes 集成本身都使用 [Fabric8
Kubernetes Client](
-{{< img src="/img/concepts/resource_lifecycle.svg" alt="Flink Resource
Lifecycle" >}}
+
-**We can
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
caicancai commented on PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809#issuecomment-2071289098 squashed -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [FLINK-34970] Translate architecture documents into Chinese [flink-kubernetes-operator]
1996fanrui merged PR #809: URL: https://github.com/apache/flink-kubernetes-operator/pull/809 -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
