Kestra 2.0 Engine Rewrite and Deployment Flexibility

说明与用途

Kestra 2.0 将系统拆分为控制平面和数据平面，使工作器可以在不需要数据库访问的隔离网络中运行，提升灵活性和安全性。

问题

Organizations struggled with Kestra’s heavy architecture requiring Kafka and Elasticsearch clusters, limiting deployment flexibility and causing security teams to avoid using it.

结果

Kestra 2.0 enables secure, scalable orchestration in isolated or multi-cloud environments without requiring heavy infrastructure, improving adoption and reducing operational friction.

工作流

• 1. Deploy control plane (scheduler, executor, webserver, indexer, worker controller) in desired location.
• 2. Configure queue (e.g., JDBC) and repository (e.g., PostgreSQL) for control plane.
• 3. Deploy workers in target environment (cloud, on-prem, isolated network).
• 4. Workers open persistent gRPC stream to worker controller; authenticate via TLS, client cert or JWT.
• 5. Submit jobs from control plane; workers execute and return results over same stream.
• 6. Monitor via UI or logs; adjust quotas, trigger conditions, or loop constructs as needed.

证据

In 1.x, every worker needed a connection to the central database. That single design decision dictated where you were allowed to run tasks.

来源

2.0 splits Kestra into a control plane and a data plane. The executor, the scheduler, the webserver, the indexer and a new worker controller live in the control plane, and none of them run user code.

来源