feat: HW req for onprem installation. (#18608)
* feat: HW req for onprem installation. * Apply suggestions from code review * Update docs/netdata-cloud/netdata-cloud-on-prem/installation.md Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> * Apply suggestions from code review * small changes in wording --------- Co-authored-by: Fotis Voutsas <fotis@netdata.cloud>
Mateusz Bularz committed
Sep 25, 2024 at 10:49 UTC
99eed4690a35890a746b4f986e4d7de95a5c1d97
1 file changed
+12
docs/netdata-cloud/netdata-cloud-on-prem/installation.md
+12
@@ -10,6 +10,18 @@ The following components are required to install Netdata Cloud On-Prem:
10
- **Helm** version 3.12+ with OCI Configuration (explained in the installation section)
11
- **Kubectl**
12
13
+The minimum requirements for Netdata-Cloud are:
14
+- 4 CPU cores
15
+- 15GiB of memory
16
+- Cloud services are ephemeral
17
+
18
+The requirements for the non-production Dependencies helm chart:
19
+- 8 CPU cores
20
+- 14GiB of memory
21
+- 160GiB for PVCs (SSD)
22
+
23
+> **_NOTE:_** Values for each component may vary depending on the type of load. The most compute-intensive task that the On-Prem needs to perform is the initial sync of directly connected Agents. The testing for these requirements was conducted with 1,000 nodes directly connected to the On-Prem. If you plan on spawning hundreds of new nodes within a few minutes, Postgres will be the first bottleneck. For example, a 2 vCPU / 8 GiB memory / 1k IOPS database can handle 1,000 nodes without any problems if your environment is fairly steady, adding nodes in batches of 10-30 (directly connected).
24
+
25
## Preparations for Installation
26
27
### Configure AWS CLI