Apache SeaTunnel k8s 集群模式 Zeta 引擎部署指南

修改configmap中的配置kubectleditcmhazelcast修改集群地址这里采用的是headlessservice访问模式一般pod之间访问其格式为ltpod-namegt.ltservice-namegt.ltnamespacegt.svc.cluster.local

1714464130193fe734740590bf011a0130cd3727fe8b1

转载自小虾米0.0
SeaTunnel提供了一种运行Zeta引擎(Cluster-mode)的方法,可以让Kubernetes在本地运行Zeta引擎,实现更高效的应用程序部署和管理。在本文中,我们将探索SeaTunnel在k8s集群模式下运行zeta引擎的更多信息,了解如何更好地利用Zeta引擎的优势。

  1. 将SeaTunnel上传至服务器上。我之前已经解压并执行过install-plugin.sh,这里为了方便,我直接用的执行过install-plugin.sh脚本之后的seatunnel做演示。

执行过install-plugin后的lib目录包含如下:

17144641282543bbb3463e991cc493feee2b36abfcae1

tar -zxvf apache-seatunnel-2.3.3-bin.tar.gz
sh apache-seatunnel-2.3.3/bin/install-plugin.sh
tar -czvf apache-seatunnel-2.3.3-bin.tar.gz apache-seatunnel-2.3.3
  1. 构建seatunnel镜像。在安装seatunnel的同级文件夹下创建Dockerfile。配置如下,可自行选择版本:
FROM openjdk:8
ENV SEATUNNEL_HOME="/opt/seatunnel"
ENV SEATUNNEL_VERSION="2.3.3"
COPY /apache-seatunnel-${SEATUNNEL_VERSION}-bin.tar.gz /opt/apache-seatunnel-${SEATUNNEL_VERSION}-bin.tar.gz
WORKDIR /opt
RUN tar -xzvf apache-seatunnel-${SEATUNNEL_VERSION}-bin.tar.gz
RUN mv apache-seatunnel-${SEATUNNEL_VERSION} seatunnel
RUN rm -f /opt/apache-seatunnel-${SEATUNNEL_VERSION}-bin.tar.gz
WORKDIR /opt/seatunnel

执行命令

docker build -t seatunnel:2.3.3 -f Dockerfile.
  1. 查看镜像
docker images

如下所示镜像

1714464128263945fee3f6b3cb61d102fe35850818c44

  1. 将镜像load进k8s,这里用的minikube做演示
minikube image load seatunnel:2.3.3

上述可参考:手把手教你掌握SeaTunnel k8s运行Zeta引擎本地模式的技巧

  1. 创建configmap如下
kubectl create configmap hazelcast-client --from-file= config/hazelcast-client.yaml
kubectl create configmap hazelcast --from-file=config/hazelcast.yaml
kubectl create configmap seatunnelmap --from-file=config/seatunnel.yaml
  1. 使用Reloader实现更新configmap后自动重启pod
wget https://raw.githubusercontent.com/stakater/Reloader/master/deployments/kubernetes/reloader.yaml

kubectl apply -f reloader.yaml

17144641282679a3ce6f67222fad7c246995941f71972

  1. 创建seatunnel-cluster.yml如下
apiVersion: v1
kind: Service
metadata:
name: seatunnel
spec:
selector:
app: seatunnel
ports:
- port: 5801
name: seatunnel
clusterIP: None
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: seatunnel
annotations:
configmap.reloader.stakater.com/reload: "hazelcast,hazelcast-client,seatunnelmap"
spec:
serviceName: "seatunnel"
replicas: 3
selector:
matchLabels:
app: seatunnel
template:
metadata:
labels:
app: seatunnel
spec:
containers:
- name: seatunnel
image: seatunnel:2.3.3
imagePullPolicy: IfNotPresent
ports:
- containerPort: 5801
name: client
command: ["/bin/sh","-c","/opt/seatunnel/bin/seatunnel-cluster.sh -DJvmOption=-Xms2G -Xmx2G"]
resources:
limits:
cpu: "1"
memory: 4G
requests:
cpu: "1"
memory: 2G
volumeMounts:
- mountPath: "/opt/seatunnel/config/hazelcast.yaml"
name: hazelcast
subPath: hazelcast.yaml
- mountPath: "/opt/seatunnel/config/hazelcast-client.yaml"
name: hazelcast-client
subPath: hazelcast-client.yaml
- mountPath: "/opt/seatunnel/config/seatunnel.yaml"
name: seatunnelmap
subPath: seatunnel.yaml
volumes:
- name: hazelcast
configMap:
name: hazelcast
- name: hazelcast-client
configMap:
name: hazelcast-client
- name: seatunnelmap
configMap:
name: seatunnelmap
  1. 执行
kubectl apply -f seatunnel-cluster.yml

17144641282310a9fe0043cf7743775a2b6ff0397df0e

17144641282729dbf6562b22702377bdb3d22735b06aa

  1. 修改configmap中的配置
kubectl edit cm hazelcast
修改集群地址
这里采用的是headless service访问模式
一般pod之间访问其格式为 <pod-name>.<service-name>.<namespace>.svc.cluster.local

如下示例

  • seatunnel-0.seatunnel.default.svc.cluster.local
  • seatunnel-1.seatunnel.default.svc.cluster.local
  • seatunnel-2.seatunnel.default.svc.cluster.local

友情提示:不要用tab,用空格 。不然会报错

1714464128269034861108f52fdc8f9a621c227c67295

kubectl edit cm hazelcast-client

171446412926729586006aab419c914d4a8166baa9265

kubectl edit cm seatunnelmap

1714464129241102777d6a8e81e7cb95634fcb3df0355

此处改为自己的hdfs地址。
10. 可以看到如下

1714464129293da912410a985bc2e8f29ebf062397d4c

11. 待所有节点都更新完毕处于running状态后 可进入容器内查看路径是否已修改

kubectl exec -it seatunnel-0 /bin/bash
cat config/hazelcast.yaml

171446412924089ef2261a062b84941903682217bad87

  1. 在容器内查看日志
tail -200f logs/seatunnel-engine-server.log

1714464129485ec3af66a38777c800ecab89cebaf0ced

我们发现集群已经正常运行.

  1. 运行任务

我们可以再新打开一个连接,登录另一个pod节点执行任务来测试集群:

kubectl exec -it seatunnel-1 /bin/bash
bin/seatunnel.sh --config config/v2.streaming.conf.template

我们发现其他pod内也已经开始运行任务

17144641294928cb3bcf0718780d8a162e28a5e0a1ed5

原文链接:https://blog.csdn.net/weixin_41854429/article/details/132836402