Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi team! We have multiple data processing pipelines currently deployed as separate services on EKS using Helm charts. We're exploring Flyte to potentially:
1. Connect these pipelines into cohesive workflows
2. Better manage their execution lifecycle
3. Handle dependencies between pipelines
What's the recommended approach? Should we keep Helm for deployments and use Flyte for orchestration, or migrate everything to be Flyte-native? Looking for best practices in integrating Flyte with existing EKS-deployed services :thinking_face:

Migrating to Flyte will make it faster to iterate and work with

You can start with connecting first and then migrating 

does Flyte need a seperate k8s cluster? or it can be inside a namespace in our cluster?
I mean what's the best option here?

You can run in your cluster - again recommendation is separate cluster if you want to start running large compute through it