You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by fa...@apache.org on 2022/06/20 09:10:48 UTC
[incubator-seatunnel] branch dev updated: [Doc] update seatunnel doc on kubernetes (#2035)
This is an automated email from the ASF dual-hosted git repository.
fanjia pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/incubator-seatunnel.git
The following commit(s) were added to refs/heads/dev by this push:
new 14e606611 [Doc] update seatunnel doc on kubernetes (#2035)
14e606611 is described below
commit 14e6066119b2ad2bdcf2da20efe2eb5048f005ea
Author: Hisoka <fa...@apache.org>
AuthorDate: Mon Jun 20 17:10:42 2022 +0800
[Doc] update seatunnel doc on kubernetes (#2035)
* update contribute-plugin.md about plugin mapping.
* update contribute-plugin.md about plugin mapping.
* update seatunnel doc on kubernetes
* Update kubernetes.mdx
change 2.1.0 to 2.1.2
Co-authored-by: TrickyZerg <32...@users.noreply.github.com>
---
docs/en/start/kubernetes.mdx | 38 ++++++++++++++++++++------------------
pom.xml | 2 +-
2 files changed, 21 insertions(+), 19 deletions(-)
diff --git a/docs/en/start/kubernetes.mdx b/docs/en/start/kubernetes.mdx
index bc867d1a2..740901da7 100644
--- a/docs/en/start/kubernetes.mdx
+++ b/docs/en/start/kubernetes.mdx
@@ -7,7 +7,7 @@ import TabItem from '@theme/TabItem';
# Set Up with Kubernetes
-This section provides a quick guide to using SeaTunnel with Kubernetes.
+This section provides a quick guide to using SeaTunnel with Kubernetes.
## Prerequisites
@@ -42,26 +42,28 @@ To run the image with SeaTunnel, first create a `Dockerfile`:
```Dockerfile
FROM flink:1.13
-ENV SEATUNNEL_VERSION="2.1.0"
+ENV SEATUNNEL_VERSION="2.1.2"
+ENV SEATUNNEL_HOME = "/opt/seatunnel"
+
+RUN mkdir -p $SEATUNNEL_HOME
RUN wget https://archive.apache.org/dist/incubator/seatunnel/${SEATUNNEL_VERSION}/apache-seatunnel-incubating-${SEATUNNEL_VERSION}-bin.tar.gz
RUN tar -xzvf apache-seatunnel-incubating-${SEATUNNEL_VERSION}-bin.tar.gz
-RUN mkdir -p $FLINK_HOME/usrlib
-RUN cp apache-seatunnel-incubating-${SEATUNNEL_VERSION}/lib/seatunnel-core-flink.jar $FLINK_HOME/usrlib/seatunnel-core-flink.jar
-
-RUN rm -fr apache-seatunnel-incubating-${SEATUNNEL_VERSION}*
+RUN cp -r apache-seatunnel-incubating-${SEATUNNEL_VERSION}/* $SEATUNNEL_HOME/
+RUN rm -rf apache-seatunnel-incubating-${SEATUNNEL_VERSION}*
+RUN rm -rf $SEATUNNEL_HOME/connectors/spark
```
Then run the following commands to build the image:
```bash
-docker build -t seatunnel:2.1.0-flink-1.13 -f Dockerfile .
+docker build -t seatunnel:2.1.2-flink-1.13 -f Dockerfile .
```
-Image `seatunnel:2.1.0-flink-1.13` need to be present in the host (minikube) so that the deployment can take place.
+Image `seatunnel:2.1.2-flink-1.13` need to be present in the host (minikube) so that the deployment can take place.
-Load image to minikube via:
+Load image to minikube via:
```bash
-minikube image load seatunnel:2.1.0-flink-1.13
+minikube image load seatunnel:2.1.2-flink-1.13
```
</TabItem>
@@ -77,7 +79,7 @@ minikube image load seatunnel:2.1.0-flink-1.13
]}>
<TabItem value="flink">
-The steps below provide a quick walk-through on setting up the Flink Kubernetes Operator.
+The steps below provide a quick walk-through on setting up the Flink Kubernetes Operator.
Install the certificate manager on your Kubernetes cluster to enable adding the webhook component (only needed once per Kubernetes cluster):
@@ -118,7 +120,7 @@ flink-kubernetes-operator-5f466b8549-mgchb 1/1 Running 3 (23h
<TabItem value="flink">
In this guide we are going to use [flink.streaming.conf](https://github.com/apache/incubator-seatunnel/blob/dev/config/flink.streaming.conf.template):
-
+
```conf
env {
execution.parallelism = 1
@@ -143,7 +145,7 @@ sink {
```
This configuration need to be present when we are going to deploy the application (SeaTunnel) to Flink cluster (on Kubernetes), we also need to configure a Pod to Use a PersistentVolume for Storage.
-- Create `/mnt/data` on your Node. Open a shell to the single Node in your cluster. How you open a shell depends on how you set up your cluster. For example, in our case weare using Minikube, you can open a shell to your Node by entering `minikube ssh`.
+- Create `/mnt/data` on your Node. Open a shell to the single Node in your cluster. How you open a shell depends on how you set up your cluster. For example, in our case weare using Minikube, you can open a shell to your Node by entering `minikube ssh`.
In your shell on that Node, create a /mnt/data directory:
```bash
minikube ssh
@@ -166,7 +168,7 @@ metadata:
namespace: default
name: seatunnel-flink-streaming-example
spec:
- image: seatunnel:2.1.0-flink-1.13
+ image: seatunnel:2.1.2-flink-1.13
flinkVersion: v1_14
flinkConfiguration:
taskmanager.numberOfTaskSlots: "2"
@@ -180,7 +182,7 @@ spec:
resource:
memory: "2048m"
cpu: 2
- podTemplate:
+ podTemplate:
spec:
containers:
- name: flink-main-container
@@ -194,8 +196,8 @@ spec:
type: Directory
job:
- jarURI: local:///opt/flink/usrlib/seatunnel-core-flink.jar
- entryClass: org.apache.seatunnel.SeatunnelFlink
+ jarURI: local:///opt/seatunnel/lib/seatunnel-core-flink.jar
+ entryClass: org.apache.seatunnel.core.flink.SeatunnelFlink
args: ["--config", "/data/flink.streaming.conf"]
parallelism: 2
upgradeMode: stateless
@@ -264,5 +266,5 @@ Happy SeaTunneling!
## What's More
-For now, you are already taking a quick look at SeaTunnel, you could see [connector](/category/connector) to find all source and sink SeaTunnel supported.
+For now, you are already taking a quick look at SeaTunnel, you could see [connector](/category/connector) to find all source and sink SeaTunnel supported.
Or see [deployment](../deployment.mdx) if you want to submit your application in another kind of your engine cluster.
diff --git a/pom.xml b/pom.xml
index fc98c929d..6fba87ac3 100644
--- a/pom.xml
+++ b/pom.xml
@@ -88,7 +88,7 @@
</modules>
<properties>
- <revision>2.1.1-SNAPSHOT</revision>
+ <revision>2.1.3-SNAPSHOT</revision>
<seatunnel.config.shade.version>2.1.1</seatunnel.config.shade.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<java.version>1.8</java.version>