STAC-22815: Document 4000 profile

Author: aacevedoosorio

k8s-suse-rancher-prime.md

@@ -23,21 +23,22 @@ To install SUSE Observability, ensure that the nodes have enough CPU and memory
 
 There are different installation options available for SUSE Observability. It is possible to install SUSE Observability either in a High-Availability (HA) or single instance (non-HA) setup. The non-HA setup is recommended for testing purposes or small environments. For production environments, it is recommended to install SUSE Observability in a HA setup.
 
-The HA production setup can support from 150 up to 500 Nodes (a Node is counted as<= 4 vCPU and <= 16GB Memory) under observation.
+The HA production setup can support from 150 up to 4000 Nodes (a Node is counted as <= 4 vCPU and <= 16GB Memory) under observation.
 The Non-HA setup can support up to 100 Nodes under observation.
 
-| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| **CPU Requests** | 7,5 | 7,5 | 10,5 | 15 | 25 | 49 | 62 | 86.5 |
-| **CPU Limits** | 16 | 16 | 21,5 | 30,5 | 50 | 103 | 128 | 176 |
-| **Memory Requests** | 22Gi | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi |
-| **Memory Limits** | 23Gi | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |
+| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |  --- |
+| **CPU Requests** | 7,5 | 7,5 | 10,5 | 15 | 25 | 49 | 62 | 86.5 | 210 |
+| **CPU Limits** | 16 | 16 | 21,5 | 30,5 | 50 | 103 | 128 | 176 | 278 |
+| **Memory Requests** | 22Gi | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | 256Gi |
+| **Memory Limits** | 23Gi | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |317.5Gi |
 
 {% hint style="info" %}
 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
+* For HA installations up to 500 nodes the min recommended node size is 8VCPU, 16GB
+* For 4000 nodes HA installations the min recommended node size is 16VCPU, 32GB
 {% endhint %}
 
 {% hint style="info" %}
@@ -56,10 +57,10 @@ SUSE Observability uses persistent volume claims for the services that need to s
 
 For our different installation profiles, the following are the defaulted storage requirements:
 
-| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| **Retention (days)** | 3 | 30 | 30 | 30 | 30 | 30 | 30 | 30 |
-| **Storage requirement** | 125GB | 280GB | 420GB | 420GB | 600GB | 2TB | 2TB | 2.5TB |
+| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| **Retention (days)** | 3 | 30 | 30 | 30 | 30 | 30 | 30 | 30 | 30 |
+| **Storage requirement** | 125GB | 280GB | 420GB | 420GB | 600GB | 2TB | 2TB | 2.5TB | 2.5TB | 5.5 TB
 
 For more details on the defaults used, see the page [Configure storage](/setup/install-stackstate/kubernetes_openshift/storage.md).
 

setup/install-stackstate/requirements.md

@@ -22,18 +22,19 @@ There are different installation options available for SUSE Observability. It is
 
 In the table below you can find the resource requirements for the different installation options. For the HA setup you can find different installation profiles depending on the size of the environment being observed.
 
-| | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| **CPU Requests** | 7,5 | 10,5 | 15 | 25 | 49 | 62 | 86.5 |
-| **CPU Limits** | 16 | 21,5 | 30,5 | 50 | 103 | 128 | 176 |
-| **Memory Requests** | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi |
-| **Memory Limits** | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |
+| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |  --- |
+| **CPU Requests** | 7,5 | 7,5 | 10,5 | 15 | 25 | 49 | 62 | 86.5 | 210 |
+| **CPU Limits** | 16 | 16 | 21,5 | 30,5 | 50 | 103 | 128 | 176 | 278 |
+| **Memory Requests** | 22Gi | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | 256Gi |
+| **Memory Limits** | 23Gi | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |317.5Gi |
 
 {% hint style="info" %}
 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
+* For HA installations up to 500 nodes the min recommended node size is 8VCPU, 16GB
+* For 4000 nodes HA installations the min recommended node size is 16VCPU, 32GB
 {% 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.
@@ -52,10 +53,10 @@ SUSE Observability uses persistent volume claims for the services that need to s
 
 For our different installation profiles, the following are the defaulted storage requirements:
 
-| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| **Retention (days)** | 3 | 30 | 30 | 30 | 30 | 30 | 30 | 30 |
-| **Storage requirement** | 125GB | 280GB | 420GB | 420GB | 600GB | 2TB | 2TB | 2.5TB |
+| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| **Retention (days)** | 3 | 30 | 30 | 30 | 30 | 30 | 30 | 30 | 30 |
+| **Storage requirement** | 125GB | 280GB | 420GB | 420GB | 600GB | 2TB | 2TB | 2.5TB | 2.5TB | 5.5 TB
 
 {% hint style="info" %}
 The storage estimates presented take into account a default of 14 days of retention for NONHA and 1 month for HA installations. For short lived test instances the storage sizes can be further reduced.