You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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"?
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 ?
The text was updated successfully, but these errors were encountered: