diff --git a/modules/deployments-setting-resources.adoc b/modules/deployments-setting-resources.adoc
index 58c0013116bf..6f2bcb0b6467 100644
--- a/modules/deployments-setting-resources.adoc
+++ b/modules/deployments-setting-resources.adoc
@@ -12,6 +12,11 @@ This resource is available only if a cluster administrator has enabled the ephem
 
 A deployment is completed by a pod that consumes resources (memory, CPU, and ephemeral storage) on a node. By default, pods consume unbounded node resources. However, if a project specifies default container limits, then pods consume resources up to those limits.
 
+[NOTE]
+====
+The minimum memory limit for a deployment is 12 MB. If a container fails to start due to a `Cannot allocate memory` pod event, the memory limit is too low. Either increase or remove the memory limit. Removing the limit allows pods to consume unbounded node resources.
+====
+
 You can also limit resource use by specifying resource limits as part of the deployment strategy. Deployment resources can be used with the recreate, rolling, or custom deployment strategies.
 
 .Procedure
diff --git a/modules/nodes-cluster-resource-configure-about.adoc b/modules/nodes-cluster-resource-configure-about.adoc
index db92674adf95..276fa905a3f9 100644
--- a/modules/nodes-cluster-resource-configure-about.adoc
+++ b/modules/nodes-cluster-resource-configure-about.adoc
@@ -44,6 +44,9 @@ Note the following about memory requests and memory limits:
 
   - The cluster administrator can assign quota or assign default values for the memory limit value.
 
+  - The minimum memory limit is 12 MB. If a container fails to start due to a `Cannot allocate memory` pod event, the memory limit is too low. 
+Either increase or remove the memory limit. Removing the limit allows pods to consume unbounded node resources.
+ 
 [id="nodes-cluster-resource-configure-about-memory_{context}"]
 == Managing application memory strategy