diff --git a/logging/config/cluster-logging-log-store.adoc b/logging/config/cluster-logging-log-store.adoc
index c69c1c475ac8..d07019945335 100644
--- a/logging/config/cluster-logging-log-store.adoc
+++ b/logging/config/cluster-logging-log-store.adoc
@@ -46,6 +46,8 @@ include::modules/cluster-logging-logstore-limits.adoc[leveloffset=+1]
 
 include::modules/cluster-logging-elasticsearch-ha.adoc[leveloffset=+1]
 
+include::modules/cluster-logging-elasticsearch-scaledown.adoc[leveloffset=+1]
+
 include::modules/cluster-logging-elasticsearch-storage.adoc[leveloffset=+1]
 
 include::modules/cluster-logging-elasticsearch-persistent-storage-empty.adoc[leveloffset=+1]
diff --git a/modules/cluster-logging-elasticsearch-scaledown.adoc b/modules/cluster-logging-elasticsearch-scaledown.adoc
new file mode 100644
index 000000000000..056307831eda
--- /dev/null
+++ b/modules/cluster-logging-elasticsearch-scaledown.adoc
@@ -0,0 +1,16 @@
+// Module included in the following assemblies:
+//
+// * logging/cluster-logging-log-store.adoc
+
+[id="cluster-logging-elasticsearch-scaledown_{context}"]
+= Scaling down Elasticsearch pods
+
+Reducing the number of Elasticsearch pod in your cluster can result in data loss or Elasticsearch performance degradation. 
+
+If you scale down, you should scale down by one pod at a time and allow the cluster to re-balance the shards and replicas. After the Elasticsearch health status returns to `green`, you can scale down by another pod. 
+
+[NOTE]
+====
+If your Elasticsearch cluster is set to `ZeroRedundancy`, you should not scale down your Elasticsearch pods. 
+====
+