Summary
The user is exploring the use of different agents for production and staging namespaces, particularly in the context of canary deployments for task routing. They are unsure about the implementation details due to Kevin's absence, who has the necessary information. The user is open to further exploration but notes that current support may be limited. An update from Kevin suggests that the namespace can be modified in the agent's address. The user also proposes logging specific requests related to task types and seeks feedback on whether this is advisable for each request in the propeller. Additionally, they wish to have separate instances of their agent in each project domain to test changes in isolation without impacting production workflows.
thomas.maschler
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
eric901201
<@USU6W5ATA> Do you think it's a good idea to do this for each request in the propeller?
eric901201
maybe it's a good idea to print logs about
endpoint 1 send Create request for task type 1
eric901201
you can print logs in your corresponding agent server
thomas.maschler
Ok, thanks. But how can I make sure that for each workspace, tasks are routed to the corresponding agent?
eric901201
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"
kumare
I don’t think so this is supported today, but let Kevin be back next week
eric901201
thank you
eric901201
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
thomas.maschler
Can I use different agent for different namespaces (ie production/ staging)? I saw I can 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