DanielLeens commented on issue #12886: URL: https://github.com/apache/seatunnel/issues/12886#issuecomment-6266963156
Thanks for offering to investigate this. Classification: D / Zeta Kubernetes Application Mode HA design. I rechecked the related work: the initial Kubernetes Application Mode implementation in #12460 is merged, and I found no competing HA implementation PR. HA changes master ownership, application status, failover, cleanup, and compatibility guarantees, so this is not ready for an implementation claim or assignment. Please first add a STIP-41 follow-up/design linked to #11857 that makes the proposed multi-master control-plane contract explicit: workload kind and ownership, active-master election/fencing, durable-state and `backup-count` preconditions, client/status/cancel behavior through failover, worker-loss policy, and terminal cleanup boundaries. A PoC may validate those assumptions, but do not open a production implementation PR until the design and its K3s failure-test matrix are agreed. No label or assignment change is made here. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
