diff --git a/modules/nodes-cluster-resource-override.adoc b/modules/nodes-cluster-resource-override.adoc
index c1898bea0c..b0c45b9b51 100644
--- a/modules/nodes-cluster-resource-override.adoc
+++ b/modules/nodes-cluster-resource-override.adoc
@@ -10,6 +10,9 @@
 [role="_abstract"]
 You can use the Cluster Resource Override Operator to control the level of overcommit and manage container density across all the nodes in your cluster. The Operator, which is an admission webhook, controls how nodes in specific projects can exceed defined memory and CPU limits.
 
+:operator-name: The Cluster Resource Override Operator
+include::snippets/operator-not-available.adoc[]
+
 // Paragraph taken from 3.11 docs and modified. 
 // https://docs.openshift.com/container-platform/3.11/admin_guide/overcommit.html#configuring-masters-for-overcommitment
 The Operator modifies the ratio between the requests and limits that are set on developer containers. In conjunction with a per-project limit range that specifies limits and defaults, you can achieve the desired level of overcommit.
diff --git a/modules/rn-ocp-release-notes-known-issues.adoc b/modules/rn-ocp-release-notes-known-issues.adoc
index 4963558366..76af75bfb2 100644
--- a/modules/rn-ocp-release-notes-known-issues.adoc
+++ b/modules/rn-ocp-release-notes-known-issues.adoc
@@ -4,6 +4,8 @@
 
 This section includes several known issues for {product-title} {product-version}.
 
+* Currently, due to a known issue, the {product-title} 4.21 versions of the Cluster Resource Override Operator and the DPU Operator will be available in an upcoming 4.21 maintenance release.  (link:https://issues.redhat.com/browse/OCPBUGS-74224[OCPBUGS-74224])
+
 * If you mirrored the {product-title} release images to the registry of a disconnected environment by using the `oc adm release mirror` command, the release image Sigstore signature is not mirrored with the image.
 +
 This has become an issue in {product-title} {product-version}, because the `openshift` cluster image policy is now deployed to the cluster by default. This policy causes CRI-O to automatically verify the Sigstore signature when pulling images into a cluster.  (link:https://issues.redhat.com/browse/OCPBUGS-70297[OCPBUGS-70297])
diff --git a/networking/networking_operators/dpu-operator/dpu-operator.adoc b/networking/networking_operators/dpu-operator/dpu-operator.adoc
index a404f42ba0..64e019cb9c 100644
--- a/networking/networking_operators/dpu-operator/dpu-operator.adoc
+++ b/networking/networking_operators/dpu-operator/dpu-operator.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 As a cluster administrator, you can add the DPU Operator to your cluster to manage DPU devices and network attachments.
 
+:operator-name: The DPU Operator
+include::snippets/operator-not-available.adoc[]
+
 --
 :FeatureName: The DPU Operator
 include::snippets/technology-preview.adoc[]