Hi all, do you have any advice on the best way to ...
# ask-metaflow
p
Hi all, do you have any advice on the best way to separate metaflow metadata for multiple teams? The only solution that comes to my mind right now is to deploy separate metaflow stack for each team. Our metaflow stack is deployed on on-prem k8s cluster.
j
Arent namespaces enough? There are also projects and branches that I dont have good idea with, but I think namespaces are good enough I think namespaces are kind of fixed, but @project should be more appropriate? https://docs.metaflow.org/scaling/tagging#switching-namespaces
p
Unfortunately it isn't enough 😕 Sorry I wasn't clear enough. We want to separate metadata in such a way that people from different teams won't be able to access each other's data.
👍 1