[enterprise-4.20] OSDOCS-20786: Configuring NFD worker node selectors and tolerations.

[yashshree2002]

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

masterTolerations	<[]Object>         <<<<<<----------------
    effect	<string>
    key	<string>

 workerNodeSelector	<map[string]string>   <<<<<<------------------
  workerPriorityClassName	<string>
  workerTolerations	<[]Object>
    effect	<string>

[openshift-ci-robot]

@yashshree2002: This pull request references OSDOCS-20786 which is a valid jira issue.

Details

In response to this:

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

masterTolerations	<[]Object>         <<<<<<----------------
    effect	<string>
    key	<string>

workerNodeSelector	<map[string]string>   <<<<<<------------------
  workerPriorityClassName	<string>
  workerTolerations	<[]Object>
    effect	<string>

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @yashshree2002. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions 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.