openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPBUGS-15851: 2 NFD exceptions are not covered in product docs

Browse Source
This commit is contained in:
GroceryBoyJr
2024-12-13 16:22:42 -05:00
committed by openshift-cherrypick-robot
parent 8e3514cf9f
commit fcdfb01090
4 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
hardware_enablement/psap-node-feature-discovery-operator.adoc
View File

@@ -19,6 +19,12 @@ The Node Feature Discovery (NFD) Operator orchestrates all resources needed to r
As a cluster administrator, you can create a `NodeFeatureDiscovery` CR by using the {oc-first} or the web console.
[NOTE]
====
Starting with version 4.12, the `operand.image` field in the `NodeFeatureDiscovery` CR is mandatory. If the NFD Operator is deployed by using {olm-first}, OLM automatically sets the `operand.image` field. If you create the `NodeFeatureDiscovery` CR by using the {product-title} CLI or the {product-title} web console, you must set the `operand.image` field explicitly.
====
include::modules/creating-nfd-cr-cli.adoc[leveloffset=+2]
include::modules/creating-nfd-cr-cli-disconnected.adoc[leveloffset=+2]
include::modules/creating-nfd-cr-web-console.adoc[leveloffset=+2]

3
modules/creating-nfd-cr-cli-disconnected.adoc
View File

@@ -70,7 +70,7 @@ metadata:
name: nfd-instance
spec:
operand:
image: <mirror_registry>/openshift4/ose-node-feature-discovery@<image_digest>
image: <mirror_registry>/openshift4/ose-node-feature-discovery@<image_digest> <1>
imagePullPolicy: Always
workerConfig:
configData: |
@@ -142,6 +142,7 @@ spec:
matchOn:
- loadedKMod: ["example_kmod3"]
----
<1> The `operand.image` field is mandatory.
. Create the `NodeFeatureDiscovery` CR by running the following command:
+

3
modules/creating-nfd-cr-cli.adoc
View File

@@ -38,7 +38,7 @@ spec:
instance: "" # instance is empty by default
topologyupdater: false # False by default
operand:
image: registry.redhat.io/openshift4/ose-node-feature-discovery-rhel9:v{product-version}
image: registry.redhat.io/openshift4/ose-node-feature-discovery-rhel9:v{product-version} <1>
imagePullPolicy: Always
workerConfig:
configData: |
@@ -110,6 +110,7 @@ spec:
matchOn:
- loadedKMod: ["example_kmod3"]
----
<1> The `operand.image` field is mandatory.
. Create the `NodeFeatureDiscovery` CR by running the following command:
+

5
modules/creating-nfd-cr-web-console.adoc
View File

@@ -20,3 +20,8 @@ As a cluster administrator, you can create a `NodeFeatureDiscovery` CR by using
. In the *Node Feature Discovery* section, under *Provided APIs*, click *Create instance*.
. Edit the values of the `NodeFeatureDiscovery` CR.
. Click *Create*.
[NOTE]
====
Starting with version 4.12, the `operand.image` field in the `NodeFeatureDiscovery` CR is mandatory. If the NFD Operator is deployed by using {olm-first}, OLM automatically sets the `operand.image` field. If you create the `NodeFeatureDiscovery` CR by using the {product-title} CLI or the {product-title} web console, you must set the `operand.image` field explicitly.
====