Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple clusterqueues / localqueues with xpk #51

Open
Obliviour opened this issue Dec 21, 2023 · 1 comment
Open

Support multiple clusterqueues / localqueues with xpk #51

Obliviour opened this issue Dec 21, 2023 · 1 comment

Comments

@Obliviour
Copy link
Collaborator

xpk currently supports one cluster queue / local queue. If an xpk cluster administrator wants to split capacity between different use cases, they would currently have to create separate xpk clusters.

xpk can support multiple quotas within the same cluster by using multiple clusterqueues / localqueues.

# create a cluster that organizes resource usage limits across different queues 
xpk cluster create --quotas= {local_queue_name: device_type, num_slices, local_queue_name2: device_type, num_slices}
# xpk needs to check that the quotas are less than or equal to the quota available
# resources not specified with a quota will be sent to the default cluster kueue
# run a workload against one of the above queues (local queue name)
xpk cluster create --queue=local_queue_name
# by default the queue will be multislice-queue
# if queue doesn't exist, xpk can list the queues available in the error.
@bernardhan33
Copy link

+1. One issue here also is that the local queue is a namespaced object and currently is only created under the default namespace.

As we are aware that it is generally recommended not to run applications in the default namespace, are there considerations of improving this behavior?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants