@<1729671499981262848:profile|CooperativeKitten94> Running the following conf:

  queue:
    services-tasks:
      templateOverrides:
        resources: 
          requests:
            nvidia.com/gpu: "1"
          limits:
            nvidia.com/gpu: "1"
    services: 
      templateOverrides:
        resources: 
          requests:
            nvidia.com/gpu: "0"
          limits:
            nvidia.com/gpu: "0"


  apiServerUrlReference: "

"
  fileServerUrlReference: "
``...

And as it turnout, cannot specify multiply queues:

-- ClearML queue this agent will consume. Multiple queues can be specified with the following format: queue1,queue2,queue3

queue: default
gives an error

@<1729671499981262848:profile|CooperativeKitten94> thank you! I will try and will update : ))

Hey, ignore the above please -> I had a typo in the secret key name

I must add I do not see anything in the helmchart for using templateOverrides

Hey @<1729671499981262848:profile|CooperativeKitten94> yes, it did! 🙂
I thank you for the support.

Hey @<1798887585121046528:profile|WobblyFrog79> , yes testing this locally it does seems to solve the issue, thank you.
I will test it in our env.

On a different issue, have you any solution on how to make the agent listen to multiply queues?
On the helm it is written :

  # -- ClearML queue this agent will consume. Multiple queues can be specified with the following format: queue1,queue2,queue3

But this does not work as the agent will read them all as one queue

@<1689446563463565312:profile|SmallTurkey79> are you using the community edition with helm?
I am having the same issue here.

@<1523701087100473344:profile|SuccessfulKoala55> is this feature block by community edition maybe ?

Hey Martin, do you know how to connect the agent to multiply queues?

Hey @<1523701070390366208:profile|CostlyOstrich36>
Can you explain this point a bit more?
In the helmchart of the agent I configure like so:
...

agentk8sglue:
  extraEnvs: 
  - name: AWS_ACCESS_KEY_ID
    valueFrom:
      secretKeyRef:
        name: aws-access-key-id
        key: AWS_ACCESS_KEY_ID
  - name: AWS_SECRET_ACCESS_KEY
    valueFrom:
      secretKeyRef:
        name: aws-secret-access-key
        key: AWS_SECRET_ACCESS_KEY
  - name: K8S_GLUE_MAX_PODS
    value: '1'
  - name:...

Hey @<1523701087100473344:profile|SuccessfulKoala55>
The relevant log from the pipeline shows:

error: pathspec 'origin/${pipeline.branch}' did not match any file(s) known to git
Repository cloning failed: Command '['git', 'checkout', 'origin/$%7Bpipeline.branch%7D', '--force']' returned non-zero exit status 1.

and I believe this is because the params cannot be injected in such a way, not sure if this is a bug or normal behaviour.
I am able to to use it like so:

pipe.add_par...