My initial implementation of RBAC / Isolation is ready for a first pass. This is effectively what we run in our internal fork at Stack but with some more flexibility added to the configuration to make it less Stack biased. The diff changes most of the DB code paths when RBAC is enabled and there is no test coverage there yet but I can probably slowly work on that.

Hi @clean-glass-36808, nice to e-meet you. Thanks a lot for the contribution. We heard from our users and community, and we are working in a plan for 2025 to make Flyte feature readiness and robustness increased. I will ask you for some patience as we finalize the process, which this PR is a perfect candidate for it, as the PR is involved [touches various areas] and introduces new concepts. As you have this PR ready, I will ask the team to expedite the first draft of the process. I will get back to you ASAP.

I'll continue to add some unit tests over time. I am also working through an initial trial of this code in @shy-evening-51366’s environment

Hi @clean-glass-36808. Sorry for the delay here. The team has been heads down with the upgrades of the documentation system, and we have been working around the clock to get the best UX possible and resolve any rough edges. My plan is to get back to you on this next week, assuming 🤞 that we can finalize the docs migration to a good state by Monday. cc: @average-finland-92144

No worries

Hi @bulky-gold-93144 any indication of a timeline for getting Jason’s great work to land in a Flyte release?

hey @shy-evening-51366 one thing we have been discussing in the contributor's sync is the challenge of maintaining this great work in the long term. We leaned towards forming a SIG-RBAC (introduced here) where community members and contributors who are in a position to maintain that feature long term can volunteer and organize. In case the group is not formed, the change won't be accepted (which is by no means a function of its quality or importance) but a measure to prevent contributor burnout, or having a very critical feature not being maintained by a diverse and skilled number of individuals.

Thanks David, that sounds like a good solution 👍 looking forward!