Merge pull request #1554 from StackVista/stac-0-clarify-requiements

Add a min node size to the requirements
StackVista · Dec 5, 2024 · c6cfc06 · c6cfc06
2 parents 099ae90 + 983944b
commit c6cfc06
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/k8s-suse-rancher-prime.md b/k8s-suse-rancher-prime.md
@@ -34,7 +34,10 @@ The Non-HA setup can support up to 100 Nodes under observation.
 | **Memory Limits** | 23Gi | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |
 
 {% hint style="info" %}
-The requirement shown for profile represent the total amount of resources needed to run the Suse Observability workload, the user can decide the amount of nodes and the node size they prefer as long as the requirements are met.
+The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server.
+To ensure that all different services of Suse Observability server can be allocated:
+* For non-HA installations the recommended node size is 4VCPU, 8GB
+* For HA installations the min recommended node size is 8VCPU, 16GB
 {% endhint %}
 
 {% hint style="info" %}

diff --git a/setup/install-stackstate/requirements.md b/setup/install-stackstate/requirements.md
@@ -30,7 +30,10 @@ In the table below you can find the resource requirements for the different inst
 | **Memory Limits** | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |
 
 {% hint style="info" %}
-The requirement shown for profile represent the total amount of resources needed to run the Suse Observability workload, the user can decide the amount of nodes and the node size they prefer as long as the requirements are met.
+The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server.
+To ensure that all different services of Suse Observability server can be allocated:
+* For non-HA installations the recommended node size is 4VCPU, 8GB
+* For HA installations the min recommended node size is 8VCPU, 16GB
 {% endhint %}
 
 These are just the upper and lower bounds of the resources that can be consumed by SUSE Observability in the different installation options. The actual resource usage will depend on the features used, configured resource limits and dynamic usage patterns, such as Deployment or DaemonSet scaling. For our Self-hosted customers, we recommend to start with the default requirements and monitor the resource usage of the SUSE Observability components.