Skip to content

Commit 6df24bc

Browse files
craffitcraffit
committed
Merge remote-tracking branch 'origin/suse-observability' into suse-observability-staging
2 parents 7b721cb + 42d8296 commit 6df24bc

4 files changed

Lines changed: 21 additions & 15 deletions

File tree

‎k8s-suse-rancher-prime.md‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,17 @@ To install SUSE Observability, ensure that the nodes have enough CPU and memory
2323

2424
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.
2525

26-
The HA production setup can support from 150 up to 4000 Nodes (a Node is counted as <= 4 vCPU and <= 16GB Memory) under observation.
26+
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`.
27+
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
28+
a profile.
2729
The Non-HA setup can support up to 100 Nodes under observation.
2830

29-
| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA |
30-
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
31-
| **CPU Requests** | 7,5 | 7,5 | 10,5 | 15 | 25 | 49 | 62 | 86.5 | 210 |
32-
| **CPU Limits** | 16 | 16 | 21,5 | 30,5 | 50 | 103 | 128 | 176 | 278 |
33-
| **Memory Requests** | 22Gi | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | 256Gi |
34-
| **Memory Limits** | 23Gi | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |317.5Gi |
31+
| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA |
32+
| ------------------- | ------ | --------- | --------- | --------- | ---------- | ------ | ------- | ------- | ------- |
33+
| **CPU Requests** | 7.5 | 7.5 | 10.5 | 15 | 25 | 49 | 62 | 86.5 | 210 |
34+
| **CPU Limits** | 16 | 16 | 21.5 | 30.5 | 50 | 103 | 128 | 176 | 278 |
35+
| **Memory Requests** | 22.5Gi | 22.5Gi | 28Gi | 32Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | 256Gi |
36+
| **Memory Limits** | 23.5Gi | 23.5Gi | 29Gi | 33.5Gi | 51.5Gi | 131Gi | 147.5Gi | 166Gi | 317.5Gi |
3537

3638
{% hint style="info" %}
3739
The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server.

‎setup/install-stackstate/requirements.md‎

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,17 @@ SUSE Observability can be installed on a Kubernetes or OpenShift cluster using t
2121
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.
2222

2323
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.
24+
An observed node in this sizing table is taken to be 4 vCPUs and 16GB of memory, our `default node size`.
25+
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
26+
a profile.
2427

25-
| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA |
26-
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
27-
| **CPU Requests** | 7,5 | 7,5 | 10,5 | 15 | 25 | 49 | 62 | 86.5 | 210 |
28-
| **CPU Limits** | 16 | 16 | 21,5 | 30,5 | 50 | 103 | 128 | 176 | 278 |
29-
| **Memory Requests** | 22Gi | 22Gi | 28Gi | 32.5Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | 256Gi |
30-
| **Memory Limits** | 23Gi | 23Gi | 29Gi | 33Gi | 51,5Gi | 131Gi | 147.5Gi | 166Gi |317.5Gi |
28+
29+
| | trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA |
30+
| ------------------- | ------ | --------- | --------- | --------- | ---------- | ------ | ------- | ------- | ------- |
31+
| **CPU Requests** | 7.5 | 7.5 | 10.5 | 15 | 25 | 49 | 62 | 86.5 | 210 |
32+
| **CPU Limits** | 16 | 16 | 21.5 | 30.5 | 50 | 103 | 128 | 176 | 278 |
33+
| **Memory Requests** | 22.5Gi | 22.5Gi | 28Gi | 32Gi | 51Gi | 67Gi | 143Gi | 161.5Gi | 256Gi |
34+
| **Memory Limits** | 23.5Gi | 23.5Gi | 29Gi | 33.5Gi | 51.5Gi | 131Gi | 147.5Gi | 166Gi | 317.5Gi |
3135

3236
{% hint style="info" %}
3337
The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server.

‎setup/security/authentication/service_tokens.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ To configure SUSE Observability to create a bootstrap service token on Kubernete
6666
```yaml
6767
stackstate:
6868
authentication:
69-
servicetoken:
69+
serviceToken:
7070
bootstrap:
7171
token: <token>
7272
roles:

‎setup/upgrade-stackstate/migrate-from-6.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Throughout this guide all examples assume the following setup, customize the com
2626

2727
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):
2828

29-
* Helm chart version should be `1.12.0`
29+
* Helm chart version should be `1.12.1`
3030
* Application version should be `6.0.0-snapshot.20241023094532-stackstate-6.x-7be52ad`
3131

3232
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).

0 commit comments

Comments
 (0)