You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by fa...@apache.org on 2024/04/29 05:06:02 UTC
(flink) branch master updated: [hotfix][docs] Fix file reference
This is an automated email from the ASF dual-hosted git repository.
fanrui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new f75c5188660 [hotfix][docs] Fix file reference
f75c5188660 is described below
commit f75c51886603dfabfb10d3b1bd4fd29b3483c173
Author: caicancai <23...@qq.com>
AuthorDate: Sat Apr 27 21:51:30 2024 +0800
[hotfix][docs] Fix file reference
---
.../deployment/resource-providers/standalone/kubernetes.md | 10 +++++-----
.../deployment/resource-providers/standalone/kubernetes.md | 8 ++++----
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md b/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
index 701dd11d111..c357acd0a02 100644
--- a/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
+++ b/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
@@ -72,7 +72,7 @@ under the License.
$ kubectl create -f flink-configuration-configmap.yaml
$ kubectl create -f jobmanager-service.yaml
# 为集群创建 deployment
- $ kubectl create -f jobmanager-session-deployment.yaml
+ $ kubectl create -f jobmanager-session-deployment-non-ha.yaml
$ kubectl create -f taskmanager-session-deployment.yaml
```
@@ -91,7 +91,7 @@ $ ./bin/flink run -m localhost:8081 ./examples/streaming/TopSpeedWindowing.jar
$ kubectl delete -f jobmanager-service.yaml
$ kubectl delete -f flink-configuration-configmap.yaml
$ kubectl delete -f taskmanager-session-deployment.yaml
- $ kubectl delete -f jobmanager-session-deployment.yaml
+ $ kubectl delete -f jobmanager-session-deployment-non-ha.yaml
```
{{< top >}}
@@ -114,7 +114,7 @@ $ ./bin/flink run -m localhost:8081 ./examples/streaming/TopSpeedWindowing.jar
检查 [Application 集群资源定义](#application-cluster-resource-definitions) 并做出相应的调整：
-`jobmanager-job.yaml` 中的 `args` 属性必须指定用户作业的主类。也可以参考[如何设置 JobManager 参数]({{< ref "docs/deployment/resource-providers/standalone/docker" >}}#jobmanager-additional-command-line-arguments)来了解如何将额外的 `args` 传递给 `jobmanager-job.yaml` 配置中指定的 Flink 镜像。
+`jobmanager-application-non-ha.yaml` 中的 `args` 属性必须指定用户作业的主类。也可以参考[如何设置 JobManager 参数]({{< ref "docs/deployment/resource-providers/standalone/docker" >}}#jobmanager-additional-command-line-arguments)来了解如何将额外的 `args` 传递给 `jobmanager-application-non-ha.yaml` 配置中指定的 Flink 镜像。
*job artifacts* 可由以下方式提供：
@@ -125,7 +125,7 @@ $ ./bin/flink run -m localhost:8081 ./examples/streaming/TopSpeedWindowing.jar
在创建[通用集群组件](#common-cluster-resource-definitions)后，指定 [Application 集群资源定义](#application-cluster-resource-definitions)文件，执行 `kubectl` 命令来启动 Flink Application 集群：
```sh
- $ kubectl create -f jobmanager-job.yaml
+ $ kubectl create -f jobmanager-application-non-ha.yaml
$ kubectl create -f taskmanager-job-deployment.yaml
```
@@ -133,7 +133,7 @@ $ ./bin/flink run -m localhost:8081 ./examples/streaming/TopSpeedWindowing.jar
```sh
$ kubectl delete -f taskmanager-job-deployment.yaml
- $ kubectl delete -f jobmanager-job.yaml
+ $ kubectl delete -f jobmanager-application-non-ha.yaml
```
<a name="per-job-cluster-mode"></a>
diff --git a/docs/content/docs/deployment/resource-providers/standalone/kubernetes.md b/docs/content/docs/deployment/resource-providers/standalone/kubernetes.md
index d13796e3eb8..98f1549b7a2 100644
--- a/docs/content/docs/deployment/resource-providers/standalone/kubernetes.md
+++ b/docs/content/docs/deployment/resource-providers/standalone/kubernetes.md
@@ -113,9 +113,9 @@ A basic *Flink Application cluster* deployment in Kubernetes has three component
Check [the Application cluster specific resource definitions](#application-cluster-resource-definitions) and adjust them accordingly:
-The `args` attribute in the `jobmanager-job.yaml` has to specify the main class of the user job.
+The `args` attribute in the `jobmanager-application-non-ha.yaml` has to specify the main class of the user job.
See also [how to specify the JobManager arguments]({{< ref "docs/deployment/resource-providers/standalone/docker" >}}#jobmanager-additional-command-line-arguments) to understand
-how to pass other `args` to the Flink image in the `jobmanager-job.yaml`.
+how to pass other `args` to the Flink image in the `jobmanager-application-non-ha.yaml`.
The *job artifacts* could be provided by these way：
@@ -129,7 +129,7 @@ The *job artifacts* could be provided by these way：
After creating [the common cluster components](#common-cluster-resource-definitions), use [the Application cluster specific resource definitions](#application-cluster-resource-definitions) to launch the cluster with the `kubectl` command:
```sh
- $ kubectl create -f jobmanager-job.yaml
+ $ kubectl create -f jobmanager-application-non-ha.yaml
$ kubectl create -f taskmanager-job-deployment.yaml
```
@@ -138,7 +138,7 @@ with the `kubectl` command:
```sh
$ kubectl delete -f taskmanager-job-deployment.yaml
- $ kubectl delete -f jobmanager-job.yaml
+ $ kubectl delete -f jobmanager-application-non-ha.yaml
```
### Session Mode