From 0d58452fb1efd18dd09a0c5000f7fd01d9ce8b33 Mon Sep 17 00:00:00 2001
From: GroceryBoyJr <75502996+GroceryBoyJr@users.noreply.github.com>
Date: Wed, 14 May 2025 19:36:19 -0400
Subject: [PATCH] OSDOCS-13825: Add NOTE to CO, FIO, SPO Documentation

---
 .../co-management/compliance-operator-installation.adoc   | 6 ++++++
 .../file-integrity-operator-installation.adoc             | 5 +++++
 security/security_profiles_operator/spo-enabling.adoc     | 8 +++++++-
 3 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/security/compliance_operator/co-management/compliance-operator-installation.adoc b/security/compliance_operator/co-management/compliance-operator-installation.adoc
index a4ab202648..25443aeaa3 100644
--- a/security/compliance_operator/co-management/compliance-operator-installation.adoc
+++ b/security/compliance_operator/co-management/compliance-operator-installation.adoc
@@ -8,6 +8,12 @@ toc::[]
 
 Before you can use the Compliance Operator, you must ensure it is deployed in the cluster.
 
+[IMPORTANT]
+====
+All cluster nodes must have the same release version in order for this Operator to function properly.
+As an example, for nodes running {op-system}, all nodes must have the same {op-system} version.
+====
+
 [IMPORTANT]
 ====
 The Compliance Operator might report incorrect results on managed platforms, such as OpenShift Dedicated, Red{nbsp}Hat OpenShift Service on AWS Classic, and Microsoft Azure Red{nbsp}Hat OpenShift. For more information, see the Knowledgebase article link:https://access.redhat.com/solutions/6983418[Compliance Operator reports incorrect results on Managed Services].
diff --git a/security/file_integrity_operator/file-integrity-operator-installation.adoc b/security/file_integrity_operator/file-integrity-operator-installation.adoc
index 3497787c58..6fa054af97 100644
--- a/security/file_integrity_operator/file-integrity-operator-installation.adoc
+++ b/security/file_integrity_operator/file-integrity-operator-installation.adoc
@@ -6,6 +6,11 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[IMPORTANT]
+====
+All cluster nodes must have the same release version in order for this Operator to function properly.
+As an example, for nodes running {op-system}, all nodes must have the same {op-system} version.
+====
 
 include::modules/file-integrity-operator-installing-web-console.adoc[leveloffset=+1]
 
diff --git a/security/security_profiles_operator/spo-enabling.adoc b/security/security_profiles_operator/spo-enabling.adoc
index 2f02f57470..af8b30f8ca 100644
--- a/security/security_profiles_operator/spo-enabling.adoc
+++ b/security/security_profiles_operator/spo-enabling.adoc
@@ -8,6 +8,12 @@ toc::[]
 
 Before you can use the Security Profiles Operator, you must ensure the Operator is deployed in the cluster.
 
+[IMPORTANT]
+====
+All cluster nodes must have the same release version in order for this Operator to function properly.
+As an example, for nodes running {op-system}, all nodes must have the same {op-system} version.
+====
+
 [IMPORTANT]
 ====
 The Security Profiles Operator supports only Red Hat Enterprise Linux CoreOS (RHCOS) worker nodes. Red Hat Enterprise Linux (RHEL) nodes are not supported.
@@ -22,4 +28,4 @@ include::modules/spo-installing.adoc[leveloffset=+1]
 
 include::modules/spo-installing-cli.adoc[leveloffset=+1]
 
-include::modules/spo-logging-verbosity.adoc[leveloffset=+1]
\ No newline at end of file
+include::modules/spo-logging-verbosity.adoc[leveloffset=+1]