<@U06RKAMK0UC> In multicluster setup in data-plane...
# ask-ai
m
@ancient-wolf-19325 In multicluster setup in data-plane (propeller) - flyte uses bucket to store data passed across tasks. For entire propeller, there is just 1 s3 bucket with all the data. Inside this bucket. Ididnt find any traces of per-project split or anything. Can I somehow do RBAC so specific projects do not have acess to other project's data from propeller bucket?
a
By default, Flyte organizes data in the object store bucket using the layout
<project>/<domain>/<run-name>/<action-name>/...
, so all project data is stored under project-specific prefixes within a single bucket. However, IAM policies and bucket policies can be used to scope access to specific prefixes, enabling RBAC at the project level. This means you can restrict access so that only the appropriate service accounts or IAM roles for a given project can access their corresponding prefix in the bucket, preventing cross-project access via the object store. See Object store layout for details. You will need to configure your cloud provider's IAM or bucket policies to enforce these prefix-based restrictions, as Flyte itself does not enforce RBAC within the bucketβ€”this is handled at the storage layer. Would you like more detail on how to set up these policies for AWS S3 or another provider? Sources: - Object store layout πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @herald in the thread for followups.
m
@ancient-wolf-19325 I am reffering to flyte v1 tho. so that information might be out od date now
a
The provided data sources only describe the per-project prefix layout and RBAC options for Flyte v2, not Flyte v1. There is no explicit documentation in the sources about per-project RBAC or bucket layout for Flyte v1, so I cannot confirm if v1 supports prefix-based RBAC or a similar mechanism. Would you like more detail on Flyte v2's approach, or guidance on how to investigate your Flyte v1 deployment? Sources: - https://www.union.ai/docs/v2/union/deployment/byoc/enabling-aws-resources/ πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @herald in the thread for followups.
m
@ancient-wolf-19325 I dont need v2, I need v1 info. Can you investigate if there is any helmchart setting for that or something?
a
It seems likely that none of the provided data sources contain explicit information about Flyte v1 Helm chart settings for per-project RBAC or object store prefix isolation. The sources focus on Flyte v2 and do not mention v1-specific Helm chart options for this use case. Would you like suggestions on where to look in your v1 deployment, or help interpreting your current Helm values? Sources: - https://www.union.ai/docs/v2/union/deployment/byoc/enabling-aws-resources/ πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @herald in the thread for followups.
m
@ancient-wolf-19325 wheres currently the helmchart for flyte? I cant find in in charts directory in github. Was it moved?
a
The current Helm charts for Flyte are located in the
charts
directory of the Flyte GitHub repository, including subdirectories like
flyte-binary
,
flyte-devbox
, and
flyteconnector
. For example, see charts/flyte-binary and charts/flyte-devbox. If you do not see them, ensure you are viewing the latest branch (such as
main
), as the charts are present there. Would you like more detail on the chart structure or how to use them? Sources: - charts/flyte-binary/README.md - charts/flyte-devbox πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @herald in the thread for followups.
m
@ancient-wolf-19325 but there used to be multi-cluster flyte helmchart there. Binary is just 1-cluster thing. Devbox is useless. wheres the rest
a
The Flyte's documentation I have ingested does not mention where the older multi-cluster Flyte Helm charts (from Flyte v1) are currently located or if they have been moved or deprecated; the available charts in the current repository are primarily for the single-binary (single-cluster) deployment and the devbox demo environment. If you are looking for the legacy multi-component, multi-cluster Helm charts, please specify the exact version or component you need, or check archived branches or tags in the Flyte GitHub repository for historical chart locations. If this doesn't help, please reach out to the Flyte support team for further assistance. πŸ‘ 0 button πŸ‘Ž 0 button πŸ’‘ Hint: Mention @herald in the thread for followups.