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

SeaTunnel提供了一種運行Zeta引擎(cluster-mode)的方法，可以讓Kubernetes在本地運行Zeta引擎，實現更高效的應用程式部署和管理。在本文中，我們將探索SeaTunnel k8s運行zeta引擎(cluster-mode模式)的更多信息，瞭解如何更好地利用Zeta引擎的優勢。

1. 將SeaTunnel上傳至伺服器上。我之前已經解壓並執行過install-plugin.sh，這裡為了方便，我直接用的執行過install-plugin.sh腳本之後的seatunnel做演示。

執行過install-plugin後的lib目錄包含如下：

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

2. 構建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.

3. 查看鏡像

docker images

如下所示鏡像

4. 將鏡像load進k8s，這裡用的minikube做演示

minikube image load seatunnel:2.3.3

上述可參考：手把手教你掌握SeaTunnel k8s運行Zeta引擎本地模式的技巧

5. 創建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

6. 使用Reloader實現更新configmap後自動重啟pod

wget https://raw.githubusercontent.com/stakater/Reloader/master/deployments/kubernetes/reloader.yaml

kubectl apply -f reloader.yaml

7. 創建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

8. 執行

 kubectl apply -f seatunnel-cluster.yml

9. 修改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，用空格 。不然會報錯

kubectl edit cm hazelcast-client

kubectl edit cm seatunnelmap

此處改為自己的hdfs地址。

10. 可以看到如下

11. 待所有節點都更新完畢處於running狀態後 可進入容器內查看路徑是否已修改

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

12. 在容器內查看日誌

tail -200f logs/seatunnel-engine-server.log

我們發現集群已經正常運行.

13. 運行任務

我們可以再新打開一個連接，登錄另一個pod節點執行任務來測試集群：

kubectl exec -it seatunnel-1 /bin/bash

bin/seatunnel.sh --config config/v2.streaming.conf.template

我們發現其他pod內也已經開始運行任務

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

本文由 白鯨開源 提供發佈支持！