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

Allow the identification of "volcano nodes" #4038

Closed
jjuliogallegos01 opened this issue Feb 24, 2025 · 1 comment
Closed

Allow the identification of "volcano nodes" #4038

jjuliogallegos01 opened this issue Feb 24, 2025 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jjuliogallegos01
Copy link

What is the problem you're trying to solve

My understanding is that volcano assumes all nodes in a k8s cluster are all volcano nodes for compute intensive batch jobs.

However, there are situations in which we could have general-use k8s clusters and add a few HPC nodes to an existing cluster.

K8s provides some mechanisms to force the execution of pods in a specific group of nodes, but those mechanisms would be implemented at Pod level, meaning that the volcano scheduler may want to run a job on specific nodes, but then if we force the use of specific group of nodes at Pod level, that wouldn't be efficient for the volcano scheduler.

Describe the solution you'd like

I think we can add a parameter on the Volcano helm chart values file to identify what nodes are intended for volcano. It could be a selector based on labels or other parameters similar to pods selector.

e.g:

volcanoNodeSelector:
matchLabels:
nodeType: volcano

That allows an efficient identification of the correct nods.

Additional context

I am assuming forcing the execution of pods on specific nodes outside of volcano is not efficient.

@jjuliogallegos01 jjuliogallegos01 added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 24, 2025
@jjuliogallegos01
Copy link
Author

node groups should do it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant