Merge remote-tracking branch 'origin/suse-observability' into suse-ob…

…servability-staging
StackVista · Jan 27, 2025 · 6df24bc · 6df24bc
2 parents 7b721cb + 42d8296
commit 6df24bc
Show file tree

Hide file tree

Showing 4 changed files with 21 additions and 15 deletions.
diff --git a/k8s-suse-rancher-prime.md b/k8s-suse-rancher-prime.md
@@ -23,15 +23,17 @@ 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 4000 Nodes (a Node is counted as <= 4 vCPU and <= 16GB Memory) under observation.
+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.
 
-| | 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 |
+|                     | 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** | 22.5Gi | 22.5Gi    | 28Gi      | 32Gi      | 51Gi       | 67Gi   | 143Gi   | 161.5Gi | 256Gi   |
+| **Memory Limits**   | 23.5Gi | 23.5Gi    | 29Gi      | 33.5Gi    | 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.

diff --git a/setup/install-stackstate/requirements.md b/setup/install-stackstate/requirements.md
@@ -21,13 +21,17 @@ 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 | 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 |
+
+|                     | 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** | 22.5Gi | 22.5Gi    | 28Gi      | 32Gi      | 51Gi       | 67Gi   | 143Gi   | 161.5Gi | 256Gi   |
+| **Memory Limits**   | 23.5Gi | 23.5Gi    | 29Gi      | 33.5Gi    | 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.

diff --git a/setup/security/authentication/service_tokens.md b/setup/security/authentication/service_tokens.md
@@ -66,7 +66,7 @@ To configure SUSE Observability to create a bootstrap service token on Kubernete
 ```yaml
 stackstate:
   authentication:
-    servicetoken:
+    serviceToken:
       bootstrap:
         token: <token>
         roles:

diff --git a/setup/upgrade-stackstate/migrate-from-6.md b/setup/upgrade-stackstate/migrate-from-6.md
@@ -26,7 +26,7 @@ Throughout this guide all examples assume the following setup, customize the com
 
 Only the latest version of StackState 6.x has a configuration backup that contains all configuration in a format that is compatible with SUSE Observability. Please make sure you have the latest version installed by running `helm list --namespace stackstate` (use the namespace where StackState is installed):
 
-* Helm chart version should be `1.12.0`
+* Helm chart version should be `1.12.1`
 * Application version should be `6.0.0-snapshot.20241023094532-stackstate-6.x-7be52ad`
 
 If you don't have that version please upgrade first following the standard [upgrade steps](https://docs.stackstate.com/6.0/self-hosted-setup/upgrade-stackstate/steps-to-upgrade#minor-or-maintenance-stackstate-release).