Nfd worker scheduling - #117893
Open
GroceryBoyJr wants to merge 1 commit into
Open
Conversation
|
🤖 Thu Aug 13 00:53:21 - Prow CI generated the docs preview: |
GroceryBoyJr
force-pushed
the
nfd-worker-scheduling
branch
3 times, most recently
from
August 12, 2026 21:58
931765d to
92141fe
Compare
GroceryBoyJr
force-pushed
the
nfd-worker-scheduling
branch
9 times, most recently
from
August 13, 2026 00:40
afc1409 to
5e65bd1
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
GroceryBoyJr
force-pushed
the
nfd-worker-scheduling
branch
from
August 13, 2026 00:44
5e65bd1 to
c616779
Compare
|
@GroceryBoyJr: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current Node Feature Discovery (NFD) Operator documentation does not describe the workerNodeSelector and workerTolerations fields available under spec.operand of the NodeFeatureDiscovery custom resource.
These fields allow cluster administrators to:
Schedule NFD worker pods only on selected nodes by using workerNodeSelector.
Schedule NFD worker pods on tainted nodes by configuring workerTolerations
The masterTolerations field allows NFD master pods to tolerate taints applied to control plane/master nodes.
Beginning with Red Hat OpenShift Container Platform 4.20, the NodeFeatureDiscovery custom resource supports configuring the placement of NFD worker and master pods through the spec.operand section.
Ref:
https://github.com/openshift/cluster-nfd-operator/blob/98a074e63cd08de9748892a1d2361e33665efaf1/api/v1/nodefeaturediscovery_types.go#L112
Version(s): 4.20+
Issue: https://redhat.atlassian.net/browse/OSDOCS-XXXXX
Link to docs preview: https://117893--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_enablement/psap-node-feature-discovery-operator.html#configuring-nfd-worker-master-pod-scheduling
QE review:
[ ] QE has approved this change.