From 706f06360e6f8932f34611fbab949b300df76f5f Mon Sep 17 00:00:00 2001 From: Alejandro Acevedo Date: Tue, 3 Dec 2024 09:19:32 +0100 Subject: [PATCH] STAC-0: Clarify that the resource requirements are not per node but total for the app to run --- k8s-suse-rancher-prime.md | 4 ++++ setup/install-stackstate/requirements.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/k8s-suse-rancher-prime.md b/k8s-suse-rancher-prime.md index 6a8d42062..79a734624 100644 --- a/k8s-suse-rancher-prime.md +++ b/k8s-suse-rancher-prime.md @@ -33,6 +33,10 @@ The Non-HA setup can support up to 100 Nodes under observation. | **Memory Requests** | 22Gi | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | | **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. +{% endhint %} + {% hint style="info" %} A trial setup is a 10 non-HA setup configured with a 3 day retention and lower disk space requirements. {% endhint %} diff --git a/setup/install-stackstate/requirements.md b/setup/install-stackstate/requirements.md index 868c634a2..96f37a1c8 100644 --- a/setup/install-stackstate/requirements.md +++ b/setup/install-stackstate/requirements.md @@ -29,6 +29,10 @@ In the table below you can find the resource requirements for the different inst | **Memory Requests** | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | | **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. +{% 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. {% hint style="info" %}