You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "MonsterChenzhuo (via GitHub)" <gi...@apache.org> on 2023/05/18 13:01:57 UTC

[GitHub] [incubator-seatunnel] MonsterChenzhuo commented on pull request #4523: [WIP][Feature][Zeta] Support on k8s mode deployment

MonsterChenzhuo commented on PR #4523:
URL: https://github.com/apache/incubator-seatunnel/pull/4523#issuecomment-1553019882

   @hailin0 @kezhenxu94 
   Hazelcast indeed supports K8s deployment, but the K8s deployment I need to implement is not simply about deploying several persistent Hazelcast clusters and submitting through the client.
   
   What I need is a deployment method similar to Flink's K8s Application Mode to support the deployment of over 4000 batch tasks per day.
   
   In Application Mode, user code is bundled with the SeaTunnel engine image, as it runs the main() method of the user code on the cluster. Application Mode ensures that all SeaTunnel engine components are properly cleaned up after the application terminates.
   
   By using the Application Mode:
   
   For production use, this mode provides better isolation for applications.
   It is able to dynamically allocate and deallocate TaskManagers according to the required resources, as it can communicate directly with Kubernetes.
   It greatly simplifies the deployment, configuration, and lifecycle management of SeaTunnel engine resources on Kubernetes.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org