diff --git a/docs/faqs/cloud-cost-management-faqs.md b/docs/faqs/cloud-cost-management-faqs.md
index 94bde13602..9ac92b29d6 100644
--- a/docs/faqs/cloud-cost-management-faqs.md
+++ b/docs/faqs/cloud-cost-management-faqs.md
@@ -296,8 +296,6 @@ All inventory metrics are pulled in once every hour.
 
 CCM has a data retention policy per edition. After this period, the data is deleted and no longer available.
 
-
-
 |  |  |  |
 | --- | --- | --- |
 | **Free** | **Team** | **Enterprise** |
@@ -307,6 +305,19 @@ CCM has a data retention policy per edition. After this period, the data is dele
 The hourly granularity of cluster data is retained for 14 days. After 14 days, CCM retains daily granularity of the data.
 :::
 
+
+### What are the recommended resource allocations for different delegate cluster sizes?
+
+thering fine-grain metrics in the cluster is memory intensive.  In an effort to ensure we don't run out of memory and terminate the pod, the following sizing guidelines are recommended:
+
+| # Nodes in the Cluster | CPU (Cores) | MEM (Mi)  |
+| -----------------------| ----------- | --------- |
+|        `<= 100`        |      1      |    3814   |
+|       `101 - 200`      |      2      |    7629   |
+|       `201 - 300`      |      3      |   11444   |
+|       `301 - 400`      |      4      |   15258   |
+|       `401 - 500`      |      5      |   19073   |
+
 ## On-premises
 
 #### Does CCM support on-premises platform installations?
diff --git a/kb/cloud-cost-management/cloud-cost-management-faqs.md b/kb/cloud-cost-management/cloud-cost-management-faqs.md
index b4e6913901..e5a812a137 100644
--- a/kb/cloud-cost-management/cloud-cost-management-faqs.md
+++ b/kb/cloud-cost-management/cloud-cost-management-faqs.md
@@ -78,6 +78,19 @@ Sometimes Azure takes time to propagate/refresh the access settings on the stora
 
 There is no data retention present for CCM. However, all data that is older than 5 years old is deleted.
 
+### What are the recommended resource allocations for different delegate cluster sizes?
+
+thering fine-grain metrics in the cluster is memory intensive.  In an effort to ensure we don't run out of memory and terminate the pod, the following sizing guidelines are recommended:
+
+| # Nodes in the Cluster | CPU (Cores) | MEM (Mi)  |
+| -----------------------| ----------- | --------- |
+|        `<= 100`        |      1      |    3814   |
+|       `101 - 200`      |      2      |    7629   |
+|       `201 - 300`      |      3      |   11444   |
+|       `301 - 400`      |      4      |   15258   |
+|       `401 - 500`      |      5      |   19073   |
+
+
 ## Perspectives
 
 ### Can the order of perspectives in the list be customized for alerting purposes?