diff --git a/installing/installing-logging.adoc b/installing/installing-logging.adoc
index 73524a4837b3..cc9b3a5c5156 100644
--- a/installing/installing-logging.adoc
+++ b/installing/installing-logging.adoc
@@ -20,6 +20,7 @@ You can use either the {ocp-product-title} web console or the {ocp-product-title
 [IMPORTANT]
 ====
 You must configure the {clo} after the {loki-op}.
+You must install the {clo} and the {loki-op} with the same major and minor version.
 ====
 
 
diff --git a/upgrading/upgrading-to-logging-60.adoc b/upgrading/upgrading-to-logging-60.adoc
index 557434fceeda..7d3600d57a05 100644
--- a/upgrading/upgrading-to-logging-60.adoc
+++ b/upgrading/upgrading-to-logging-60.adoc
@@ -26,6 +26,11 @@ include::modules/logging-oc-explain.adoc[leveloffset=+1]
 
 The only managed log storage solution available in this release is a Lokistack, managed by the *loki-operator*. This solution, previously available as the preferred alternative to the managed Elasticsearch offering, remains unchanged in its deployment process.
 
+[IMPORTANT]
+====
+You must install the {clo} and the {loki-op} with the same major and minor version.
+====
+
 [IMPORTANT]
 ====
 To continue using an existing Red Hat managed Elasticsearch or Kibana deployment provided by the *elasticsearch-operator*, remove the owner references from the `Elasticsearch` resource named `elasticsearch`, and  the `Kibana` resource named `kibana` in the `openshift-logging` namespace before removing the `ClusterLogging` resource named `instance` in the same namespace.