Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
1996fanrui merged PR #810: URL: https://github.com/apache/flink-kubernetes-operator/pull/810 -- 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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1590735382
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,95 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担人工操作 Flink 部署的职责。 人工操作者对 Flink
部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator 的主要目标是使这些活动自动化，而这无法仅通过
Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+- 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - Application 集群
+ - Session 集群
+ - Sessio job
Review Comment:
```suggestion
- Session job
```
--
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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1584453635
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+ - 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 将作业顶点调整到合适的并行度
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}})
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1584453151
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+ - 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 将作业顶点调整到合适的并行度
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}})
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1584451630
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+ - 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
Review Comment:
done
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1584445284
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
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.
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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1584443822
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+ - 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
Review Comment:
- Application 集群
- Session 集群
- Sessio job
?
--
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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
1996fanrui commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1582842831
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
Review Comment:
How about translate `human operator` to `人工操作` or `手动操作`?
Flink Kubernetes Operator 旨在承担人工操作 Flink 部署的职责。 人工操作者对 Flink
部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+ - 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1581796658
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -104,6 +122,7 @@ drwxr-xr-x 2 60 May 12 09:46
a6031ec7-ab3e-4b30-ba77-6498e58e6b7f
drwxr-xr-x 2 60 May 11 15:11 b6fb2a9c-d1cd-4e65-a9a1-e825c4b47543
```
-### AuditUtils can log sensitive information present in the custom resources
-As reported in
[FLINK-30306](https://issues.apache.org/jira/browse/FLINK-30306) when Flink
custom resources change the operator logs the change, which could include
sensitive information. We suggest ingesting secrets to Flink containers during
runtime to mitigate this.
-Also note that anyone who has access to the custom resources already had
access to the potentially sensitive information in question, but folks who only
have access to the logs could also see them now. We are planning to introduce
redaction rules to AuditUtils to improve this in a later release.
+
Review Comment:
```suggestion
```
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
-- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human operator 的职责。Human
Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator
的主要目标是使这些活动自动化，而这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 处理错误，回滚失败的升级
+ - 多 Flink 版本支持：v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 将作业顶点调整到合适的并行度
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ -
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1581788600
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments , 这是 human Operator 的职责。
human Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
Operator 的主要目标是这些活动的自动化，这无法仅通过 Flink 原生集成来实现。
Review Comment:
done
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
Review Comment:
no
--
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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1581788552
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments , 这是 human Operator 的职责。
human Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
Operator 的主要目标是这些活动的自动化，这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
Review Comment:
done
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running,
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1581788455
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments , 这是 human Operator 的职责。
human Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
Operator 的主要目标是这些活动的自动化，这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{<
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1581788381
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -104,6 +122,7 @@ drwxr-xr-x 2 60 May 12 09:46
a6031ec7-ab3e-4b30-ba77-6498e58e6b7f
drwxr-xr-x 2 60 May 11 15:11 b6fb2a9c-d1cd-4e65-a9a1-e825c4b47543
```
-### AuditUtils can log sensitive information present in the custom resources
-As reported in
[FLINK-30306](https://issues.apache.org/jira/browse/FLINK-30306) when Flink
custom resources change the operator logs the change, which could include
sensitive information. We suggest ingesting secrets to Flink containers during
runtime to mitigate this.
-Also note that anyone who has access to the custom resources already had
access to the potentially sensitive information in question, but folks who only
have access to the logs could also see them now. We are planning to introduce
redaction rules to AuditUtils to improve this in a later release.
+
Review Comment:
done
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments , 这是 human Operator 的职责。
human Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
Operator 的主要目标是这些活动的自动化，这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810: URL: https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1578934746 ## docs/content.zh/docs/concepts/overview.md: ## @@ -104,6 +122,7 @@ drwxr-xr-x 2 60 May 12 09:46 a6031ec7-ab3e-4b30-ba77-6498e58e6b7f drwxr-xr-x 2 60 May 11 15:11 b6fb2a9c-d1cd-4e65-a9a1-e825c4b47543 ``` -### AuditUtils can log sensitive information present in the custom resources -As reported in [FLINK-30306](https://issues.apache.org/jira/browse/FLINK-30306) when Flink custom resources change the operator logs the change, which could include sensitive information. We suggest ingesting secrets to Flink containers during runtime to mitigate this. -Also note that anyone who has access to the custom resources already had access to the potentially sensitive information in question, but folks who only have access to the logs could also see them now. We are planning to introduce redaction rules to AuditUtils to improve this in a later release. + Review Comment: ```suggestion ``` We should keep the `-` style at the link anchors in the whole page. BTW:I am not sure if it is necessary to lowercase all characters, which needs to be consistent with the English title format. Would you mind checking and making adjustments? -- 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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1578923881
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments , 这是 human Operator 的职责。
human Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
Operator 的主要目标是这些活动的自动化，这无法仅通过 Flink 原生集成来实现。
+
+
+
+
+## 特征
+
+
+
+### 核心
+- 全自动 [Job Lifecycle Management]({{< ref "docs/custom-resource/job-management"
>}})
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
Review Comment:
多 Flink 版本支持：v1.15，v1.16，v1.17，v1.18
--
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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574398142
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
Review Comment:
ignored ?
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+
+
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和 [operator
模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为
Kubernetes 本地部署体验的核心。
+
+Flink Kubernetes Operator 旨在承担管理 Flink deployments , 这是 human Operator 的职责。
human Operators 对 Flink 部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。
Operator 的主要目标是这些活动的自动化，这无法仅通过 Flink 原生集成来实现。
Review Comment:
```suggestion
Flink Kubernetes Operator 旨在承担管理 Flink deployments，这是 human Operator
的职责。human Operators 对 Flink
部署应该如何运行、如何启动集群、如何部署作业、如何升级作业以及出现问题时如何反应有着深入的了解。Operator 的主要目标是这些活动的自动化，而这无法仅通过
Flink 原生集成来实现。
```
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,78 +24,96 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
-
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
-
-## Features
-### Core
-- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574944960
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{< ref "docs/operations/helm" >}})
- - Automated [RBAC configuration]({{< ref "docs/operations/rbac" >}})
- - Advanced customization techniques
-- Up-to-date public
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574944960
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{< ref "docs/operations/helm" >}})
- - Automated [RBAC configuration]({{< ref "docs/operations/rbac" >}})
- - Advanced customization techniques
-- Up-to-date public
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574944490
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{< ref "docs/operations/helm" >}})
- - Automated [RBAC configuration]({{< ref "docs/operations/rbac" >}})
- - Advanced customization techniques
-- Up-to-date public
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574944144
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
Review Comment:
At first, I thought it was good not to translate. I translated
Fully-automated, but I didn’t think it was necessarily appropriate.
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810: URL: https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574942660 ## docs/content.zh/docs/concepts/overview.md: ## @@ -24,86 +24,93 @@ specific language governing permissions and limitations under the License. --> -# Overview -Flink Kubernetes Operator acts as a control plane to manage the complete deployment lifecycle of Apache Flink applications. Although Flink’s native Kubernetes integration already allows you to directly deploy Flink applications on a running Kubernetes(k8s) cluster, [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) and the [operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have also become central to a Kubernetes native deployment experience. + -Flink Kubernetes Operator aims to capture the responsibilities of a human operator who is managing Flink deployments. Human operators have deep knowledge of how Flink deployments ought to behave, how to start clusters, how to deploy jobs, how to upgrade them and how to react if there are problems. The main goal of the operator is the automation of these activities, which cannot be achieved through the Flink native integration alone. +# 概述 +Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink 的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但 [自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) 和 [operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为 Kubernetes 本地部署体验的核心。 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. 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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574941355
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许您直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{< ref "docs/operations/helm" >}})
- - Automated [RBAC configuration]({{< ref "docs/operations/rbac" >}})
- - Advanced customization techniques
-- Up-to-date public repositories
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810: URL: https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574940019 ## docs/content.zh/docs/concepts/overview.md: ## @@ -24,86 +24,93 @@ specific language governing permissions and limitations under the License. --> -# Overview -Flink Kubernetes Operator acts as a control plane to manage the complete deployment lifecycle of Apache Flink applications. Although Flink’s native Kubernetes integration already allows you to directly deploy Flink applications on a running Kubernetes(k8s) cluster, [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) and the [operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have also become central to a Kubernetes native deployment experience. + -Flink Kubernetes Operator aims to capture the responsibilities of a human operator who is managing Flink deployments. Human operators have deep knowledge of how Flink deployments ought to behave, how to start clusters, how to deploy jobs, how to upgrade them and how to react if there are problems. The main goal of the operator is the automation of these activities, which cannot be achieved through the Flink native integration alone. +# 概述 +Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink 的原生 Kubernetes 集成已经允许您直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但 [自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) 和 [operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为 Kubernetes 本地部署体验的核心。 Review Comment: done ## docs/content.zh/docs/concepts/overview.md: ## @@ -24,86 +24,93 @@ specific language governing permissions and limitations under the License. --> -# Overview -Flink Kubernetes Operator acts as a control plane to manage the complete deployment lifecycle of Apache Flink applications. Although Flink’s native Kubernetes integration already allows you to directly deploy Flink applications on a running Kubernetes(k8s) cluster, [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) and the [operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have also become central to a Kubernetes native deployment experience. + -Flink Kubernetes Operator aims to capture the responsibilities of a human operator who is managing Flink deployments. Human operators have deep knowledge of how Flink deployments ought to behave, how to start clusters, how to deploy jobs, how to upgrade them and how to react if there are problems. The main goal of the operator is the automation of these activities, which cannot be achieved through the Flink native integration alone. +# 概述 +Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink 的原生 Kubernetes 集成已经允许您直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但 [自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) 和 [operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为 Kubernetes 本地部署体验的核心。 -## Features -### Core +Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如 kubectl）管理和操作 Flink 部署。Operator的核心功能包括： 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. 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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574364314
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{< ref "docs/operations/helm" >}})
- - Automated [RBAC configuration]({{< ref "docs/operations/rbac" >}})
- - Advanced customization techniques
-- Up-to-date public
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574122219
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job Autoscaler]({{< ref "docs/custom-resource/autoscaler" >}})
- - Collect lag and utilization metrics
- - Scale job vertices to the ideal parallelism
- - Scale up and down as the load changes
-### Operations
+ - 收集延迟和利用率指标
+ - 根据指标自动调整任务管理器数量
+ - 根据负载的变化进行扩展和缩减
+
+
+
+### 运营
- Operator [Metrics]({{< ref "docs/operations/metrics-logging#metrics" >}})
- - Utilizes the well-established [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
- - Pluggable metrics reporters
- - Detailed resources and kubernetes api access metrics
+ - 使用成熟的 [Flink Metric
System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics)
+ - 可插拔的指标报告器
+ - 详细的资源和 kubernetes api 访问指标
- Fully-customizable [Logging]({{< ref
"docs/operations/metrics-logging#logging" >}})
- - Default log configuration
- - Per job log configuration
- - Sidecar based log forwarders
-- Flink Web UI and REST Endpoint Access
- - Fully supported Flink Native Kubernetes [service expose
types](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
- - Dynamic [Ingress templates]({{< ref "docs/operations/ingress" >}})
+ - 默认日志配置
+ - 每个作业日志配置
+ - 基于 sidecar 的日志转发器
+- Flink Web UI 和 REST 端点访问
+ - 完整支持 Flink 原生 Kubernetes
[服务暴露类型](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#accessing-flinks-web-ui)
+ - 通过 [Ingress 模板]({{< ref "docs/operations/ingress" >}}) 动态暴露服务
- [Helm based installation]({{< ref "docs/operations/helm" >}})
- - Automated [RBAC configuration]({{< ref "docs/operations/rbac" >}})
- - Advanced customization techniques
-- Up-to-date public
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1574054494
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
Review Comment:
```suggestion
Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink
应用程序，但[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)和
[operator 模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
```
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许你直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator 的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
Review Comment:
just a minor sus: why not do translation for these lines ?
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on code in PR #810: URL: https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1573750686 ## docs/content.zh/docs/concepts/overview.md: ## @@ -24,86 +24,93 @@ specific language governing permissions and limitations under the License. --> -# Overview -Flink Kubernetes Operator acts as a control plane to manage the complete deployment lifecycle of Apache Flink applications. Although Flink’s native Kubernetes integration already allows you to directly deploy Flink applications on a running Kubernetes(k8s) cluster, [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) and the [operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have also become central to a Kubernetes native deployment experience. + -Flink Kubernetes Operator aims to capture the responsibilities of a human operator who is managing Flink deployments. Human operators have deep knowledge of how Flink deployments ought to behave, how to start clusters, how to deploy jobs, how to upgrade them and how to react if there are problems. The main goal of the operator is the automation of these activities, which cannot be achieved through the Flink native integration alone. +# 概述 +Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink 的原生 Kubernetes 集成已经允许您直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但 [自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) 和 [operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) 也已成为 Kubernetes 本地部署体验的核心。 Review Comment: thank you -- 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-34980] Translate overview document into Chinese [flink-kubernetes-operator]
RocMarshal commented on code in PR #810:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/810#discussion_r1566975727
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许您直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
Review Comment:
https://github.com/apache/flink-kubernetes-operator/assets/64569824/2bb91f1f-8b3e-4f93-8dbd-a546f43ac4ca;>
https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications
##
docs/content.zh/docs/concepts/overview.md:
##
@@ -24,86 +24,93 @@ specific language governing permissions and limitations
under the License.
-->
-# Overview
-Flink Kubernetes Operator acts as a control plane to manage the complete
deployment lifecycle of Apache Flink applications. Although Flink’s native
Kubernetes integration already allows you to directly deploy Flink applications
on a running Kubernetes(k8s) cluster, [custom
resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
and the [operator
pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) have
also become central to a Kubernetes native deployment experience.
+
-Flink Kubernetes Operator aims to capture the responsibilities of a human
operator who is managing Flink deployments. Human operators have deep knowledge
of how Flink deployments ought to behave, how to start clusters, how to deploy
jobs, how to upgrade them and how to react if there are problems. The main goal
of the operator is the automation of these activities, which cannot be achieved
through the Flink native integration alone.
+# 概述
+Flink Kubernetes Operator 扮演控制平面的角色，用于管理 Apache Flink 应用程序的完整部署生命周期。尽管 Flink
的原生 Kubernetes 集成已经允许您直接在运行的 Kubernetes(k8s) 集群上部署 Flink 应用程序，但
[自定义资源](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
和
[operator模式](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
也已成为 Kubernetes 本地部署体验的核心。
-## Features
-### Core
+Flink Kubernetes Operator 通过自定义资源定义（CRD）来扩展 Kubernetes API，以便通过本地 k8s 工具（如
kubectl）管理和操作 Flink 部署。Operator的核心功能包括：
+
+
+
+## 特征
+
+
+
+### 核心
- Fully-automated [Job Lifecycle Management]({{< ref
"docs/custom-resource/job-management" >}})
- - Running, suspending and deleting applications
- - Stateful and stateless application upgrades
- - Triggering and managing savepoints
- - Handling errors, rolling-back broken upgrades
+ - 运行、暂停和删除应用程序
+ - 有状态和无状态应用程序升级
+ - 保存点的触发和管理
+ - 任务管理器的扩展和缩减
- Multiple Flink version support: v1.15, v1.16, v1.17, v1.18
- [Deployment Modes]({{< ref
"docs/custom-resource/overview#application-deployments" >}}):
- - Application cluster
- - Session cluster
- - Session job
+ - 应用程序集群
+ - 会话集群
+ - 会话作业
- Built-in [High
Availability](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/)
- Extensible framework
- [Custom validators]({{< ref
"docs/operations/plugins#custom-flink-resource-validators" >}})
- [Custom resource listeners]({{< ref
"docs/operations/plugins#custom-flink-resource-listeners" >}})
- Advanced [Configuration]({{< ref "docs/operations/configuration" >}})
management
- - Default configurations with dynamic updates
- - Per job configuration
- - Environment variables
+ - 默认配置与动态更新
+ - 作业配置
+ - 任务管理器配置
- POD augmentation via [Pod Templates]({{< ref
"docs/custom-resource/pod-template" >}})
- - Native Kubernetes POD definitions
- - Layering (Base/JobManager/TaskManager overrides)
+ - 原生Kubernetes POD定义
+ - 用于自定义容器和资源
- [Job
Re: [PR] [FLINK-34980] Translate overview document into Chinese [flink-kubernetes-operator]
caicancai commented on PR #810: URL: https://github.com/apache/flink-kubernetes-operator/pull/810#issuecomment-2056897700 @RocMarshal PATL，thank you -- 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
