Additionally, the k8s glue queue is internal to the operation of the agent and used as an intermediate queue. The agent spawned by the chart monitors a different queue, usually the default
queue
@<1523701087100473344:profile|SuccessfulKoala55> Thanks for the clarification; it helped! Is there a way to run directly on the k8s agent using the CLI or another method without cloning an existing task and enqueuing it?
@<1523701087100473344:profile|SuccessfulKoala55> never mind I found the answer to use task.execute_remotely
.. ty
@<1595587997728772096:profile|MuddyRobin9> , the helm chart already runs the agent, that script is not relevant for a k8s cluster