From 4a5bd0001b44a8c6c5138a5e69f3cfd3107eb173 Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Wed, 19 Nov 2025 11:46:21 +0100 Subject: [PATCH 1/4] STAC-0: Some clarification around sizing --- .../modules/en/pages/k8s-suse-rancher-prime.adoc | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc index a902b796..3a241ce2 100644 --- a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc +++ b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc @@ -21,14 +21,17 @@ A license key for SUSE Observability server can be obtained via the SUSE Custome === Requirements -To install SUSE Observability, ensure that the nodes have enough CPU and memory capacity. Below are the specific requirements. +To install SUSE Observability, ensure that the cluster has enough CPU and memory capacity. Below are the specific requirements. 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 4000 observed nodes. An observed node in this sizing table is taken to be 4 vCPUs and 16GB of memory, our `default node size`. If nodes in your observed cluster are bigger, they can count for multiple `default nodes`, so a node of 12vCPU and 48GB counts as 3 `default nodes` under observation when picking a profile. -The Non-HA setup can support up to 100 Nodes under observation. +The Non-HA setup can support up to 100 `default nodes` under observation. + + +The following table describes the resources required to deploy the SUSE Observability server in a cluster, given the amount of `default nodes` that will be observed and whether the installation should be HA or not. |=== | | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA @@ -96,9 +99,9 @@ NOTE: An additional 20% of resources is required for pod (unequal) distribution, 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 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 +* For non-HA installations the minimum per-node size is 4VCPU, 8GB +* For HA installations up to 500 nodes the minimum per-node size is 8VCPU, 16GB +* For 4000 nodes HA installations the minimum per-node size is 16VCPU, 32GB ==== From 23fb967064441ca6dabb58fae97081661481039f Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Wed, 19 Nov 2025 14:09:29 +0100 Subject: [PATCH 2/4] Update docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc Co-authored-by: akashraj4261 --- docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc index 3a241ce2..69427105 100644 --- a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc +++ b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc @@ -31,7 +31,7 @@ a profile. The Non-HA setup can support up to 100 `default nodes` under observation. -The following table describes the resources required to deploy the SUSE Observability server in a cluster, given the amount of `default nodes` that will be observed and whether the installation should be HA or not. +The following table describes the resources required to deploy the {stackstate-product-name} server in a cluster, given the amount of `default nodes` that will be observed and whether the installation should be HA or not. |=== | | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA From 40566d6a77aedf853988aada9e93d06f66e483b9 Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Wed, 19 Nov 2025 14:09:35 +0100 Subject: [PATCH 3/4] Update docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc Co-authored-by: akashraj4261 --- docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc index 69427105..94e4c7e8 100644 --- a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc +++ b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc @@ -96,7 +96,7 @@ NOTE: An additional 20% of resources is required for pod (unequal) distribution, [NOTE] ==== -The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server. +The requirement shown for profile represent the total amount of resources needed to run the {stackstate-product-name} server. To ensure that all different services of Suse Observability server can be allocated: * For non-HA installations the minimum per-node size is 4VCPU, 8GB From 745a08ffa10bacc3ad1f021bfde2d7ac3d637f8d Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Wed, 19 Nov 2025 14:09:42 +0100 Subject: [PATCH 4/4] Update docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc Co-authored-by: akashraj4261 --- docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc index 94e4c7e8..778a1f72 100644 --- a/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc +++ b/docs/latest/modules/en/pages/k8s-suse-rancher-prime.adoc @@ -23,7 +23,7 @@ A license key for SUSE Observability server can be obtained via the SUSE Custome To install SUSE Observability, ensure that the cluster has enough CPU and memory capacity. Below are the specific requirements. -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. +There are different installation options available for {stackstate-product-name}. It is possible to install {stackstate-product-name} 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 {stackstate-product-name} in a HA setup. The HA production setup can support from 150 up to 4000 observed nodes. An observed node in this sizing table is taken to be 4 vCPUs and 16GB of memory, our `default node size`. If nodes in your observed cluster are bigger, they can count for multiple `default nodes`, so a node of 12vCPU and 48GB counts as 3 `default nodes` under observation when picking