As a new adopter to use Metaflow with EKS and Argoworkflows, is there a way to “lock down” Argo. Meaning users can only view scheduled workflows instead of able to create new ones via the UI ?

it depends on how Argo UI is deployed with respect to auth, if you use "server" mode there I think it should be possible to run it with read-only permissions on workflow and workflowtemplate resources

Yeah, i'm using the example provided at https://github.com/outerbounds/terraform-aws-metaflow/blob/master/examples/eks_argo/argo.tf#L47 I think i'll be needing to study up more on how the inner workings of ArgoWorkflows works, seems like there are plenty of tuning/tweaks i'll have to do to fit our usecase 🙂