Questo contenuto non è disponibile nella lingua selezionata.
Chapter 3. Recommended resource requirements for Red Hat Advanced Cluster Security for Kubernetes
The recommended resource guidelines were developed by performing a focused test that created the following objects across a given number of namespaces:
- 10 deployments, with 3 pod replicas in a sleep state, mounting 4 secrets, 4 config maps
- 10 services, each one pointing to the TCP/8080 and TCP/8443 ports of one of the previous deployments
- 1 route pointing to the first of the previous services
- 10 secrets containing 2048 random string characters
- 10 config maps containing 2048 random string characters
During the analysis of results, the number of deployments is identified as a primary factor for increasing of used resources. And we are using the number of deployments for the estimation of required resources.
3.1. Central services (self-managed) Copia collegamentoCollegamento copiato negli appunti!
If you are using Red Hat Advanced Cluster Security Cloud Service (RHACS Cloud Service), you do not need to review the requirements for Central services, because they are managed by Red Hat. You only need to look at the requirements for secured cluster services.
Central services contain the following components:
- Central
- Central DB
- StackRox Scanner
- Scanner V4
3.1.1. Central Copia collegamentoCollegamento copiato negli appunti!
3.1.1.1. Memory and CPU requirements Copia collegamentoCollegamento copiato negli appunti!
The following table lists the minimum memory and CPU values required to run Central. To determine sizing, consider the following data:
- The total number of monitored deployments across all secured clusters that are connected to a single Central deployment
- The number of concurrent web portal users
Deployments | Concurrent web portal users | CPU | Memory |
---|---|---|---|
< 25,000 | 1 user | 2 cores | 8 GiB |
< 25,000 | < 5 users | 2 cores | 8 GiB |
< 50,000 | 1 user | 2 cores | 12 GiB |
< 50,000 | < 5 users | 6 cores | 16 GiB |
3.1.2. Central DB Copia collegamentoCollegamento copiato negli appunti!
3.1.2.1. Memory and CPU requirements Copia collegamentoCollegamento copiato negli appunti!
The following table lists the minimum memory and CPU values required to run Central DB. To determine sizing, consider the following data:
- The total number of monitored deployments across all secured clusters that are connected to a single Central deployment
- The number of concurrent web portal users
Deployments | Concurrent web portal users | CPU | Memory |
---|---|---|---|
< 25,000 | 1 user | 12 cores | 32 GiB |
< 25,000 | < 5 users | 24 cores | 32 GiB |
< 50,000 | 1 user | 16 cores | 32 GiB |
< 50,000 | < 5 users | 32 cores | 32 GiB |
3.1.3. StackRox Scanner Copia collegamentoCollegamento copiato negli appunti!
The following table lists the minimum memory and CPU values required for the StackRox Scanner deployment in the Central cluster. The table includes the number of unique images deployed in all secured clusters.
Number of unique Images | Replicas | CPU | Memory |
---|---|---|---|
< 100 | 1 replica | 1 core | 1.5 GiB |
< 500 | 1 replica | 2 cores | 2.5 GiB |
< 2000 | 2 replicas | 2 cores | 2.5 GiB |
< 5000 | 3 replicas | 2 cores | 2.5 GiB |
3.1.4. Scanner V4 Copia collegamentoCollegamento copiato negli appunti!
The following table lists the minimum memory and CPU values required for the Scanner V4 deployment in the Central cluster. The table includes the number of unique images deployed in all secured clusters.
3.1.4.1. Scanner V4 Indexer Copia collegamentoCollegamento copiato negli appunti!
Number of unique images | Replicas | CPU | Memory |
---|---|---|---|
< 100 | 1 | 2 cores | 0.5 GiB |
< 500 | 1 | 2 cores | 0.5 GiB |
< 2000 | 2 | 3 cores | 1 GiB |
< 5000 | 2 | 5 cores | 1 GiB |
< 10000 | 3 | 6 cores | 1.5 GiB |
3.1.4.2. Scanner V4 Matcher Copia collegamentoCollegamento copiato negli appunti!
Number of unique images | Replicas | CPU | Memory |
---|---|---|---|
< 100 | 1 | 1 core | 1.3 GiB |
< 500 | 1 | 1 core | 1.4 GiB |
< 2000 | 2 | 3 cores | 1.5 GiB |
< 5000 | 2 | 3 cores | 1.6 GiB |
< 10000 | 3 | 3 cores | 1.7 GiB |
3.1.4.3. Scanner V4 DB Copia collegamentoCollegamento copiato negli appunti!
Number of unique images | Replicas | CPU | Memory |
---|---|---|---|
< 100 | 1 | 1 core | 4.5 GiB |
< 500 | 1 | 3 cores | 5 GiB |
< 2000 | 1 | 6 cores | 6 GiB |
< 5000 | 1 | 6 cores | 6 GiB |
< 10000 | 1 | 8 cores | 6 GiB |
3.2. Secured cluster services Copia collegamentoCollegamento copiato negli appunti!
Secured cluster services contain the following components:
- Sensor
- Admission controller
Collector
NoteCollector component is not included on this page. Required resource requirements are listed on the default resource requirements page.
3.2.1. Sensor Copia collegamentoCollegamento copiato negli appunti!
Sensor monitors your Kubernetes and OpenShift Container Platform clusters. These services currently deploy in a single deployment, which handles interactions with the Kubernetes API and coordinates with Collector.
3.2.2. Memory and CPU requirements Copia collegamentoCollegamento copiato negli appunti!
The following table lists the minimum memory and CPU values required to run Sensor on a secured cluster.
Deployments | CPU | Memory |
---|---|---|
< 25,000 | 2 cores | 10 GiB |
< 50,000 | 2 cores | 20 GiB |
3.2.3. Admission controller Copia collegamentoCollegamento copiato negli appunti!
The admission controller prevents users from creating workloads that violate policies that you configure.
3.2.4. Memory and CPU requirements Copia collegamentoCollegamento copiato negli appunti!
The following table lists the minimum memory and CPU values required to run the admission controller on a secured cluster.
Deployments | CPU | Memory |
---|---|---|
< 25,000 | 0.5 cores | 300 MiB |
< 50,000 | 0.5 cores | 600 MiB |