Requirements
Overview
Requirements for SUSE Observability client (browser) can be found at the bottom of the page.
Compatibility with Rancher and Kubernetes
Check out the compatibility page here Rancher/Kubernetes compatibility
Resource 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 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.0 |
7.0 |
9.3 |
14.0 |
23.6 |
49.6 |
61.6 |
85.1 |
212.1 |
CPU Limits |
15.1 |
15.1 |
19.4 |
28.8 |
47.9 |
105.2 |
128.3 |
176.2 |
281 |
Memory Requests |
22.7Gi |
22.7Gi |
26.5Gi |
30.9Gi |
47.0Gi |
127.0Gi |
142.1Gi |
166.4Gi |
263.9Gi |
Memory Limits |
23.3Gi |
23.3Gi |
27.2Gi |
31.0Gi |
47.2Gi |
131.8Gi |
146.7Gi |
171.2Gi |
321.7Gi |
|
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:
|
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.
|
The minimum requirements do not include spare CPU/Memory capacity to ensure smooth application rolling updates. |
For installation of SUSE Observability please follow the installation instructions provided below:
Storage
SUSE Observability uses persistent volume claims for the services that need to store data. The default storage class for the cluster will be used for all services unless this is overridden by values specified on the command line or in a values.yaml file. All services come with a pre-configured volume size that should be good to get you started, but can be customized later using variables as required.
|
For production environments, NFS is not recommended and supported for storage provisioning in SUSE Observability due to the potential risk of data corruption. |
For our different installation profiles, the following are the defaulted storage requirements:
| trial | 10 non-HA | 20 non-HA | 50 non-HA | 100 non-HA | 150 HA | 250 HA | 500 HA | 4000 HA | |
|---|---|---|---|---|---|---|---|---|---|
Retention (days) |
3 |
30 |
30 |
30 |
30 |
30 |
30 |
30 |
30 |
Storage requirement |
163GB |
358GB |
401GB |
508GB |
562GB |
2.8TB |
2.9TB |
3.9TB |
7.5TB |
|
The storage estimates presented take into account a default of 14 days of retention for NONHA and 1 month for HA installations. For short lived test instances the storage sizes can be further reduced. |
For more details on the defaults used, see the page Configure storage.
Namespace resource limits
It isn’t recommended to set a ResourceQuota as this can interfere with resource requests. The resources required by SUSE Observability will vary according to the features used, configured resource limits and dynamic usage patterns, such as Deployment or DaemonSet scaling.
If it’s necessary to set a ResourceQuota for your implementation, the namespace resource limit should be set to match the node sizing requirements.