From 3e02bfab8a67e81787e0b1eab205c7fa6d506625 Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Wed, 22 Jan 2025 10:38:40 +0100 Subject: [PATCH] STAC-22270: Put explanation also in requirements --- setup/install-stackstate/requirements.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/setup/install-stackstate/requirements.md b/setup/install-stackstate/requirements.md index 1bdc5a6b6..34a903042 100644 --- a/setup/install-stackstate/requirements.md +++ b/setup/install-stackstate/requirements.md @@ -21,6 +21,9 @@ SUSE Observability can be installed on a Kubernetes or OpenShift cluster using t 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 only. For production environments, it is recommended to install SUSE Observability in a HA setup. For a standard, production, deployment, the SUSE Observability Helm chart will deploy many services in a redundant setup with 3 instances of each service. 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. +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. | | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | | ------------------- | ------ | --------- | --------- | --------- | ---------- | ------ | ------- | ------- |