can nfd-worker runs on specific nodes?

[wlane]

Currently, the nfd-worker runs by default on all available worker nodes. Are there any user-defined parameters to specify which nodes it should run on? I only need it to run on certain nodes with a specific label. Thanks.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[marquiz]

@yevgeny-shnaidman does the operator have possibility to set nodeSelector for the worker?

/remove-lifecycle stale

[yevgeny-shnaidman]

no, we don''t have any such field in the CRD. We can add it , if needed, but on the other hand, does it really matter if they run on all the nodes? It does not interfere with the other functionalities, and the footprint is not not big

[bernhardloos]

This is really annoying on clusters with Windows worker nodes because the NFD image is not available for it but the DaemonSet still schedules pods on them which will lead to unfix able errors in monitoring systems.

[yevgeny-shnaidman]

@if this is the only issue, then i think the better solution it to make operator add the node selector labels to the worker DS based on arch type label without any interference from the CRD

[bernhardloos]

That would be enough from my use-case and a lot simpler.