Well, you can always change the k8s glue code to be able to set pod labels based on task properties. If that's a valuable addition and works for you, we would love a PR 🙂

SuccessfulKoala55 I know it. Here is an example. I have a queue named q1 and two groups, which are used to manage the quota of our platform. In this situation, all tasks which may belong to group1 or group2 will be enqueued into the q1. And ClearML Agent K8S glue will watch the q1 and pull tasks from it. However, K8S does not know the group which this task uses except this information can be get from task. I can solve this problem by creating queues for every group. But there are too many groups (maybe over 50), I think this is not a good idea. So is there any solution which may be more elegant?

Hi FloppyDeer99 ,
When using the ClearML Agent K8S glue, you provide a pod template - in that template, under the metadata.labels section you can specify any number of custom labels you'd like to set on the pods started by the K8s glue