👋 Hello, team! I am from Autonomous Driving Department, NIO. I am investigating on the probability to use flyte for our algorithm development. Looking forward to have more communication with you buddies.

Hi @strong-barista-29632, Welcome to Flyte. Tagging @freezing-airport-6809 , your point of contact to discuss more on this.

@strong-barista-29632 welcome to the community. Let me know how we can help

welcome @strong-barista-29632

@strong-barista-29632 how’s it going?

Hi @freezing-airport-6809, Sorry for the late reply. Just a little busy with working stuffs. I spend some of my spare time investigating on the flyte now, specially for the extension part so as to be compatible with some our existing infrastructure. Will come up when there is some actual progress or problem. Thank for the consideration!

@strong-barista-29632 we are actually going to make backend extensions very was soon, so let us know if you have any issues and want to discuss

@freezing-airport-6809 Wow, that sounds cool! This should be a common feature when trying to integrate flyte to the existing pipeline, especially when some of the components, e.g., GPU clusters are managed by other people in other teams. It would be convenient if actions like creating resources can support some general approach, for example, by sending HTTP requests.

It does exist today, just that it has to be written in golang and compiled into flytepropeller - with the new change you could write it in python and still work from the backend