Update 05_environment_provisioning.adoc

Added warning
redhat-ai-services · Nov 22, 2024 · dfa201f · dfa201f
1 parent 0341f43
commit dfa201f
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/content/modules/ROOT/pages/05_environment_provisioning.adoc b/content/modules/ROOT/pages/05_environment_provisioning.adoc
@@ -20,6 +20,8 @@ The first cluster where we will run our demonstration projects requires a little
 . Change the the **Control Plane Instance Type** to **m6a.4xlarge**, as the default machine configuration does not have sufficient compute resources for the additional component we will be installing.
 . You should be able to use the default version of OpenShift, however since there are continuous releases it's a good idea to double check the https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/[RHOAI Documentation], under the **Supported configurations** subsection to ensure compatibility.
 
+WARNING: As of Nov 22, 2024 the Node Feature Discovery and NVIDIA Operator appear to be broken on the latest version of OpenShift (4.17), be sure to use 4.16 when building a cluster so that the taints and tolerations work correctly. This may be fixed by Red Hat Engineering soon, so this warning can be removed when the operators are compatible with latest OCP.
+
 [.bordershadow]
 image::OrderAWS_env.png[width=35%]
 
@@ -57,4 +59,4 @@ Additional questions that could be discussed for this topic:
 . I want to install a demonstration cluster that might last several months for a RHOAI evaluation period. What options are available?
 . Can we use our own AWS based OpenShift cluster, other than one from demo.redhat.com?
 . Could I install this on my own hardware, such as my desktop PC that is running a single node OpenShift cluster?
-. The topic of being able to easily repeat an installation, as discussed in the following GitOps sections may be interesting to discuss, since this means that work done to configure an environment is not lost if the environment is destroyed.
+. The topic of being able to easily repeat an installation, as discussed in the following GitOps sections may be interesting to discuss, since this means that work done to configure an environment is not lost if the environment is destroyed.