Selecting node in which to deploy virtual-kubelet pods #3135
Description
Describe the problem you are having (if any)
We have a k3s cluster with several FPGA boards attached (host processor varies between x86_64, arm64 and armhf), some of them behind NAT and some others with public IPs. Our IT department only opens ports for the control-plane node, so we are having issues with both GW and VK pods.
We have managed, thanks to the support team, to apply a nodeSelector for the WireGuard GW server and client templates, so that solves half of the issue.
Describe the solution you would like
A similar way of specifying nodeSelector properties for the VK pods as you have in the GW templates.
Describe the user value of this feature
Allow deployments in network-restricted scenarios, and enable finer granularity in heterogeneous cluster deployments (where maybe the most powerful node is the one not being used, as it is our case).
Describe your proposed solution
A similar way of specifying nodeSelector properties for the VK pods as you have in the GW templates.
Do you volunteer to implement this feature?
- I want to implement this feature
Code of Conduct
- I agree to follow this project's Code of Conduct