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

Node Selector Feature #549

Open
imanless opened this issue Jul 12, 2024 · 1 comment
Open

Node Selector Feature #549

imanless opened this issue Jul 12, 2024 · 1 comment

Comments

@imanless
Copy link

Is it possible to define a certain worker node for each lab node in the topology file, meaning one can choose which worker node should the lab node be deployed on, instead of relying on the kubernetes default scheduler?

@alexmasi
Copy link
Contributor

This is not something we have explored. Although I could see that being very useful for cases when you have a topo with some nodes requiring nested virt support and only some worker nodes that supported nested virt for example.

This may not be too difficult to add using the existing labels field:

map<string, string> labels = 4; // Metadata labels describing the node.
which get applied to the pod:
pod.ObjectMeta.Labels[label] = v

Contributions are welcome.

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