#3829 [Plugin] Flux Operator Issue created by vsoch Hi! 👋 I develop the Flux operator https://flux-framework.org/flux-operator/ which conceptually is like the MPI operator, but it brings up a Flux Framework cluster (that acts as a job) to run a scoped piece of work, akin the MPI operator. I'm interested in adding it as a plugin (and can also do the development work for it) but I wanted to check first about the order of operations. I had first cloned https://github.com/flyteorg/flyteplugins, and I started adding the operator under k8s until I noticed that the others (e.g., dask) had a DaskJob that is also defined under the flyteidl repository. So I think the correct order of operations (and what I want to check here) is: • Add the MiniClusterJob to https://github.com/flyteorg/flyteidl (and specificaily I'm interested in the purpose of these protos (example for dask) and what content to put there relative to the Flux Operator MiniCluster CRD) • Then add the MiniCluster plugin to https://github.com/flyteorg/flyteplugins using the above Are there any more pieces? Thanks for the help! I tried flyte out this week and really loved it - it already has support for several CRD I've been hoping to see in one place, so I'm eager to see support for our operator here as well. flyteorg/flyte