You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by gu...@apache.org on 2023/04/19 05:53:36 UTC
[flink] branch master updated (423cdcb99c3 -> e61fedda4de)
This is an automated email from the ASF dual-hosted git repository.
guoweijie pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
from 423cdcb99c3 [FLINK-27998][table] Upgrade Calcite from 1.29.0 to 1.30.0
new 8308d82ff96 [hotfix][docs] Fix broken links caused by FLINK-29372.
new e61fedda4de [hotfix][docs] Using `kubernetes` instead of `KubernetesHaServicesFactory` as high-availability.type for kubernetes_ha doc.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/content.zh/docs/deployment/ha/kubernetes_ha.md | 4 ++--
docs/content.zh/docs/deployment/ha/zookeeper_ha.md | 2 +-
.../docs/deployment/resource-providers/native_kubernetes.md | 4 ++--
docs/content/docs/deployment/ha/kubernetes_ha.md | 4 ++--
docs/content/docs/deployment/ha/zookeeper_ha.md | 2 +-
docs/content/docs/deployment/resource-providers/native_kubernetes.md | 4 ++--
6 files changed, 10 insertions(+), 10 deletions(-)
[flink] 02/02: [hotfix][docs] Using `kubernetes` instead of `KubernetesHaServicesFactory` as high-availability.type for kubernetes_ha doc.
Posted by gu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
guoweijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
commit e61fedda4de05c4c24b57c81b02d04aefac25346
Author: Weijie Guo <re...@163.com>
AuthorDate: Wed Apr 19 01:09:51 2023 +0800
[hotfix][docs] Using `kubernetes` instead of `KubernetesHaServicesFactory` as high-availability.type for kubernetes_ha doc.
---
docs/content.zh/docs/deployment/ha/kubernetes_ha.md | 2 +-
docs/content/docs/deployment/ha/kubernetes_ha.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/content.zh/docs/deployment/ha/kubernetes_ha.md b/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
index 260cc6af752..41ce67e287d 100644
--- a/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
+++ b/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
@@ -43,7 +43,7 @@ Kubernetes 高可用服务只能在部署到 Kubernetes 时使用。因此，当
为了启用高可用集群（HA-cluster），你必须设置以下配置项:
- [high-availability.type]({{< ref "docs/deployment/config" >}}#high-availability-type) (必要的):
-`high-availability.type` 选项必须设置为 `KubernetesHaServicesFactory`.
+`high-availability.type` 选项必须设置为 `kubernetes`.
```yaml
high-availability.type: kubernetes
diff --git a/docs/content/docs/deployment/ha/kubernetes_ha.md b/docs/content/docs/deployment/ha/kubernetes_ha.md
index 0b8e91f47f4..13f83947a43 100644
--- a/docs/content/docs/deployment/ha/kubernetes_ha.md
+++ b/docs/content/docs/deployment/ha/kubernetes_ha.md
@@ -45,7 +45,7 @@ In order to use Flink's Kubernetes HA services you must fulfill the following pr
In order to start an HA-cluster you have to configure the following configuration keys:
- [high-availability.type]({{< ref "docs/deployment/config" >}}#high-availability-type) (required):
-The `high-availability.type` option has to be set to `KubernetesHaServicesFactory`.
+The `high-availability.type` option has to be set to `kubernetes`.
```yaml
high-availability.type: kubernetes
[flink] 01/02: [hotfix][docs] Fix broken links caused by FLINK-29372.
Posted by gu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
guoweijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
commit 8308d82ff9679722ec338373f67ccade396ccdd6
Author: Weijie Guo <re...@163.com>
AuthorDate: Wed Apr 19 01:05:03 2023 +0800
[hotfix][docs] Fix broken links caused by FLINK-29372.
---
docs/content.zh/docs/deployment/ha/kubernetes_ha.md | 2 +-
docs/content.zh/docs/deployment/ha/zookeeper_ha.md | 2 +-
.../docs/deployment/resource-providers/native_kubernetes.md | 4 ++--
docs/content/docs/deployment/ha/kubernetes_ha.md | 2 +-
docs/content/docs/deployment/ha/zookeeper_ha.md | 2 +-
docs/content/docs/deployment/resource-providers/native_kubernetes.md | 4 ++--
6 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/docs/content.zh/docs/deployment/ha/kubernetes_ha.md b/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
index 57a0f4e374e..260cc6af752 100644
--- a/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
+++ b/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
@@ -42,7 +42,7 @@ Kubernetes 高可用服务只能在部署到 Kubernetes 时使用。因此，当
为了启用高可用集群（HA-cluster），你必须设置以下配置项:
-- [high-availability]({{< ref "docs/deployment/config" >}}#high-availability-1) (必要的):
+- [high-availability.type]({{< ref "docs/deployment/config" >}}#high-availability-type) (必要的):
`high-availability.type` 选项必须设置为 `KubernetesHaServicesFactory`.
```yaml
diff --git a/docs/content.zh/docs/deployment/ha/zookeeper_ha.md b/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
index d60c7537fcb..2a26f5ae2f8 100644
--- a/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
+++ b/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
@@ -34,7 +34,7 @@ Flink 利用 **[ZooKeeper](http://zookeeper.apache.org)** 在所有运行的 Job
为了启用高可用集群（HA-cluster），你必须设置以下配置项:
-- [high-availability]({{< ref "docs/deployment/config" >}}#high-availability-1) (必要的):
+- [high-availability.type]({{< ref "docs/deployment/config" >}}#high-availability-type) (必要的):
`high-availability.type` 配置项必须设置为 `zookeeper`。
<pre>high-availability.type: zookeeper</pre>
diff --git a/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md b/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
index 14e596e2ece..fa3f965e96b 100644
--- a/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
+++ b/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
@@ -340,7 +340,7 @@ Please refer to the official Kubernetes documentation on [RBAC Authorization](ht
Flink allows users to define the JobManager and TaskManager pods via template files. This allows to support advanced features
that are not supported by Flink [Kubernetes config options]({{< ref "docs/deployment/config" >}}#kubernetes) directly.
-Use [`kubernetes.pod-template-file.default`]({{< ref "docs/deployment/config" >}}#kubernetes-pod-template-file)
+Use [`kubernetes.pod-template-file.default`]({{< ref "docs/deployment/config" >}}#kubernetes-pod-template-file-default)
to specify a local file that contains the pod definition. It will be used to initialize the JobManager and TaskManager.
The main container should be defined with name `flink-main-container`.
Please refer to the [pod template example](#example-of-pod-template) for more information.
@@ -481,7 +481,7 @@ All the fields defined in the pod template that are not listed in the tables wil
<tr>
<td>image</td>
<td>Defined by the user</td>
- <td><a href="{{< ref "docs/deployment/config" >}}#kubernetes-container-image">kubernetes.container.image.ref</a></td>
+ <td><a href="{{< ref "docs/deployment/config" >}}#kubernetes-container-image-ref">kubernetes.container.image.ref</a></td>
<td>The container image will be resolved with respect to the defined precedence order for user defined values.</td>
</tr>
<tr>
diff --git a/docs/content/docs/deployment/ha/kubernetes_ha.md b/docs/content/docs/deployment/ha/kubernetes_ha.md
index 5362ba90b39..0b8e91f47f4 100644
--- a/docs/content/docs/deployment/ha/kubernetes_ha.md
+++ b/docs/content/docs/deployment/ha/kubernetes_ha.md
@@ -44,7 +44,7 @@ In order to use Flink's Kubernetes HA services you must fulfill the following pr
In order to start an HA-cluster you have to configure the following configuration keys:
-- [high-availability]({{< ref "docs/deployment/config" >}}#high-availability-1) (required):
+- [high-availability.type]({{< ref "docs/deployment/config" >}}#high-availability-type) (required):
The `high-availability.type` option has to be set to `KubernetesHaServicesFactory`.
```yaml
diff --git a/docs/content/docs/deployment/ha/zookeeper_ha.md b/docs/content/docs/deployment/ha/zookeeper_ha.md
index 828647a5af9..38173da5e3c 100644
--- a/docs/content/docs/deployment/ha/zookeeper_ha.md
+++ b/docs/content/docs/deployment/ha/zookeeper_ha.md
@@ -37,7 +37,7 @@ Flink includes scripts to [bootstrap a simple ZooKeeper](#bootstrap-zookeeper) i
In order to start an HA-cluster you have to configure the following configuration keys:
-- [high-availability]({{< ref "docs/deployment/config" >}}#high-availability-1) (required):
+- [high-availability.type]({{< ref "docs/deployment/config" >}}#high-availability-type) (required):
The `high-availability.type` option has to be set to `zookeeper`.
<pre>high-availability.type: zookeeper</pre>
diff --git a/docs/content/docs/deployment/resource-providers/native_kubernetes.md b/docs/content/docs/deployment/resource-providers/native_kubernetes.md
index 68073381814..996d99b6b5b 100644
--- a/docs/content/docs/deployment/resource-providers/native_kubernetes.md
+++ b/docs/content/docs/deployment/resource-providers/native_kubernetes.md
@@ -348,7 +348,7 @@ Please refer to the official Kubernetes documentation on [RBAC Authorization](ht
Flink allows users to define the JobManager and TaskManager pods via template files. This allows to support advanced features
that are not supported by Flink [Kubernetes config options]({{< ref "docs/deployment/config" >}}#kubernetes) directly.
-Use [`kubernetes.pod-template-file.default`]({{< ref "docs/deployment/config" >}}#kubernetes-pod-template-file)
+Use [`kubernetes.pod-template-file.default`]({{< ref "docs/deployment/config" >}}#kubernetes-pod-template-file-default)
to specify a local file that contains the pod definition. It will be used to initialize the JobManager and TaskManager.
The main container should be defined with name `flink-main-container`.
Please refer to the [pod template example](#example-of-pod-template) for more information.
@@ -489,7 +489,7 @@ All the fields defined in the pod template that are not listed in the tables wil
<tr>
<td>image</td>
<td>Defined by the user</td>
- <td><a href="{{< ref "docs/deployment/config" >}}#kubernetes-container-image">kubernetes.container.image.ref</a></td>
+ <td><a href="{{< ref "docs/deployment/config" >}}#kubernetes-container-image-ref">kubernetes.container.image.ref</a></td>
<td>The container image will be resolved with respect to the defined precedence order for user defined values.</td>
</tr>
<tr>