RBAC (Role-Based Access Control) is now available in open source Flyte as of early 2025, with project/domain isolation and authorization middleware implemented in FlyteAdmin. This feature is configurable via Helm charts, allowing you to enable RBAC and define rules for resource access at the project and domain level, and supports both cluster-scoped and namespace-scoped deployments. See the merged PR and chart updates for details on enabling and configuring RBAC in your deployment (Flyte Admin RBAC + Project/Domain Isolation, feat(charts/flyte-core): allow configuring the RBAC rules as namespace scoped, flyte-core values.yaml). Previously, RBAC was only available in managed Flyte (Union Cloud), but now open source Flyte supports it natively. You can enable RBAC by setting the appropriate flags in your Helm values and defining your access rules. Would you like more detail on how to configure or use RBAC in Flyte? Sources: - Flyte Admin RBAC + Project/Domain Isolation - feat(charts/flyte-core): allow configuring the RBAC rules as namespace scoped - flyte-core values.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.