buildkite
Configuration to listen to multiple queues
Buildkite allows configuring agents to listen to multiple queues as noted in this PR While in helm chart when we configure tags with values like below, queue name gets overridden as tags is a list of key,value pairs. tags: -queue=value1 -queue=value2
Can we have a feature to pass a list of values for queue as well ? or if it has to be under tags, may be queue can accept a list instead of string ?
👋 Hi @dhonnappa-amd, thanks for the question!
Is the idea here that the controller would query for jobs assigned to multiple queues within the same cluster or across multiple clusters? For configurations that filter jobs based on multiple matching agentQueryRules, would it be preferred that tags becomes a map[] of multiple agentQueryRules and iterates through each "key"?
Hi @petetomasik ,
Thanks for the quick response.
Yes, the idea is for the controller to query jobs assigned to multiple queues within the same cluster. As for multiple clusters, having 1:1 mapping of controller and cluster makes sense to keep it simple, but I'll leave that upto you.
If tags becomes a map, wouldn't the value of queue in tags be overwritten ? Would it be better to add a default value for queue under tags and the ability to add a list of values for queue rather than changing tags entirely ?
e.g., value would look something like this
tags:
queue:
'- queue1'
'- queue2'
Having the controller listen to multiple queues within the same cluster would be awesome. Is there a current alternative to have this functionality?
We currently do not have plan to support multi-queue setup. May I understand a bit more about your use cases?
Depending on your use cases, the resource class feature might be a good solution.
I am going to close this issue now, but feel free to reopen or raise it via Slack. 🙏🏿
