Can I use different agents for different namespaces (ie production/ staging)? I saw I could use canary deployments to route selected tasks to different agent services. But it is not clear to me how I could do such routing for different namespaces

Kevin knows the answer, but he is on vacation. To be honest, I didn't think about this question before, but I can take a look this week

I don’t think so this is supported today, but let Kevin be back next week

Update with Keivn: You can change your namespace from

"dns:///flyteagent.flyte.svc.cluster.local:8000"

to

"dns:///flyteagent.your_namespace.svc.cluster.local:8000"

Ok, thanks. But how can I make sure that for each workspace, tasks are routed to the corresponding agent?

you can print logs in your corresponding agent server

what does workspace mean here? are you talking about project & domain?

Yes, I'd like to have different instances of my agent in each of my project domains. This way I can test changes to my agent in isolation without interfering with production workflows

sounds reasonable, but we don’t support that atm. mind creating an issue here. [flyte-core]

⭐ Create a new Flyte Core Feature issue: https://github.com/flyteorg/flyte/issues/new?assignees=&labels=enhancement%2Cuntriaged&template=feature_request.yaml&title=%5BCore+feature%5D+