Hey folks - we're interested in pursuing a solution to the problems described in the RFC at https://github.com/flyteorg/flyte/issues/475 We missed contributor meeting yesterday unfortunately, and we're putting the cart a little before the horse -- but one of my team members has an updated alternative proposal (with an implementation) that we'd like to share. Since this one is a bit larger in scope - what would be the best way to try and get community alignment and a path forward?

We are not interested in supporting this in V1, as this is completely supported natively in v2

Thanks for the response on this one. I was wondering if this was an abandoned area given it's a 6 year old RFC 🙂 Any suggestions on how we might go forward here then? I definitely don't want us to build something in a private fork ... and given the feature gaps in Flyte v2 -- I think we're going to be on Flyte v1 for an indefinite amount of time.

what feature gaps?

Local-only for starters 🙂 I need to look at the docs some more to see how the equiv of ContainerTask works in local only -- but we don't give users access to containerd, so all of that orchestration and state management needs to run through a central service